Terminals, wireless communication methods, base stations and systems

Abstract

A terminal according to an embodiment of the present disclosure includes: a receiving unit for receiving configuration information relating to a physical uplink control channel (PUCCH) resource set corresponding to one or more transmission configuration indicator (TCI) states; and a control unit for determining a PUCCH resource corresponding to each TCI state on the basis of the configuration information. This embodiment of the present disclosure enables TCI state indication to be performed appropriately.

Description

Technical Field

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

Background Art

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

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

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

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

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

[0007] Therefore, this disclosure relates to a terminal that appropriately performs TCI status indication and a wireless communication method. 、 base station and system One of the objectives is to provide [this]. [Means for solving the problem]

[0008] A terminal relating to one aspect of this disclosure is multiple Configuration information regarding the Physical Uplink Control Channel (PUCCH) resource set corresponding to the Transmit Configuration Instruction (TCI) status. And, information indicating the TCI state associated with the PUCCH resource included in the PUCCH resource set, A receiving unit that receives the setting information And, information indicating the TCI state, Based on, 1 or more specific PUCCH Resources It is determined that the multiple TCI states are to be applied to the PUCCH resource other than the one or more specific PUCCH resources, and one of the multiple TCI states is applied to the PUCCH resource other than the one or more specific PUCCH resources. of It is determined to apply. It has a control unit that does the following. [Effects of the Invention]

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

[0010] [Figure 1] Figures 1A and 1B show an example of communication between a mobile device and a transmission point (e.g., RRH). [Figure 2] Figures 2A and 2C show examples of schemes 0 to 2 related to SFN. [Figure 3] Figures 3A and 3B show an example of Scheme 1. [Figure 4] Figures 4A to 4C show an example of a Doppler pre-compensation scheme. [Figure 5] Figure 5 shows an example of simultaneous beam renewal across multiple CCs. [Figure 6] Figures 6A and 6B show an example of a common beam. [Figure 7] Figures 7A and 7B show examples of single-DCI-based multi-TRP transmission and multi-DCI-based multi-TRP transmission, respectively. [Figure 8] Figures 8A and 8B show examples of TCI fields within DCI. [Figure 9] Figures 9A and 9B show an example of setting / instructing the joint TCI state in a single DCI-based multi-TRP. [Figure 10] Figures 10A and 10B show an example of setting / instructing the separate TCI state in a single DCI-based multi-TRP. [Figure 11] Figures 11A and 11B show an example of setting / instructing the joint TCI state corresponding to the first value of the CORESET pool index in a multi-DCI-based multi-TRP. [Figure 12] Figures 12A and 12B show an example of setting / instructing the joint TCI state corresponding to the second value of the CORESET pool index in a multi-DCI-based multi-TRP. [Figure 13] Figures 13A and 13B show examples of CC-specific TCI state pools and CC-common TCI state pools, respectively. [Figure 14] FIG. 14 is a diagram showing an example of the setting of the CC list according to Embodiment 1-2-B. [Figure 15] FIG. 15 is a diagram showing another example of the setting of the CC list according to Embodiment 1-2-B. [Figure 16] FIG. 16 is a diagram showing an example of the determination of the TCI state according to Embodiments 2-1 / 2-2. [Figure 17] FIG. 17 is a diagram showing an example of the determination of the TCI state according to Embodiment 2-3. [Figure 18] FIG. 18 is a diagram showing an example of the determination of the TCI state according to Embodiment 2-4. [Figure 19] FIGS. 19A and 19B are diagrams showing an example of joint ACK / NACK feedback and separate ACK / NACK feedback, respectively. [Figure 20] FIG. 20 is a diagram showing an example of a method for setting PUCCH resources according to Embodiment 3-1. [Figure 21] FIG. 21 is a diagram showing an example of a method for setting PUCCH resources according to Embodiment 3-2. [Figure 22] FIG. 22 is a diagram showing an example of a method for setting PUCCH resources according to Modification 1 of Embodiment 3-2. [Figure 23] FIG. 23 is a diagram showing an example of a method for setting PUCCH resources according to Modification 2 of Embodiment 3-2. [Figure 24] FIG. 24 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 25] FIG. 25 is a diagram showing an example of the configuration of a base station according to an embodiment. [Figure 26] FIG. 26 is a diagram showing an example of the configuration of a user terminal according to an embodiment. [Figure 27] FIG. 27 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to an embodiment. [Figure 28] FIG. 28 is a diagram showing an example of a vehicle according to an embodiment.

MODE FOR CARRYING OUT THE INVENTION

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

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

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

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

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

[0016] QCL may have multiple types (QCL types). For example, there may be four QCL types A and D that differ in the parameters (or parameter sets) that can be assumed to be the same, and these parameters (which may also be called QCL parameters) are shown below: • 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 assumption by the UE that one control resource set (CORESET), channel, or reference signal is in a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be called a QCL assumption.

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

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

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

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

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

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

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

[0025] QCL type A RS is always set for PDCCH and PDSCH, and QCL type D RS may be set additionally. Because it is difficult to estimate Doppler shift, delay, etc. from a single shot of DMRS reception, QCL type A RS is used to improve channel estimation accuracy. QCL type D RS is used for receiving beam determination when DMRS is received.

[0026] For example, TRS1-1, 1-2, 1-3, and 1-4 are transmitted, and TRS1-1 is advertised as QCL type C / D RS by the PDSCH's TCI state. By advertising the TCI state, the UE can use information obtained from past periodic TRS1-1 reception / measurement results to receive / channel estimate the DMRS for the PDSCH. In this case, the PDSCH's QCL source 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 in a DCI having a TCI field. The TCI state for PDSCH is indicated by the TCI field. The TCI field in DCI format 1-1 is 3 bits, and the TCI field in DCI format 1-2 is up to 3 bits.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0047] Multiple TRPs (e.g., TRP #1, #2) may be connected by an ideal / non-ideal backhaul, and information, data, etc., may be exchanged. Each TRP in a multi-TRP may transmit a different code word (CW) and a different layer. Non-coherent joint transmission (NCJT) may be used as one form of multi-TRP transmission.

[0048] In NCJT, for example, TRP#1 modulates and layers a first codeword and transmits a first PDSCH using a first precode with a first number of layers (e.g., 2 layers). TRP#2 modulates and layers a second codeword and transmits a second PDSCH using a second precode with a second number of layers (e.g., 2 layers).

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

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

[0051] Multiple PDSCHs from a multi-TRP (sometimes called multiple PDSCHs) may be scheduled using a single DCI (single DCI, single PDCCH) (single-master mode, single-DCI based multi-TRP). Multiple PDSCHs from a multi-TRP may each be scheduled using multiple DCIs (multi-DCI, multiple PDCCH) (multi-master mode, multi-DCI based multi-TRP).

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

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

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

[0055] A UE may be determined to be a multi-TRP based on multi-DCI if at least one of the following conditions 1 and 2 is met. In this case, TRP may be interpreted as a CORESET pool index. [Condition 1] A CORESET pool index of 1 is set. [Condition 2] Two different values ​​(e.g., 0 and 1) are set for the CORESET pool index.

[0056] The UE may determine a single DCI-based multi-TRP if the following conditions are met. In this case, the two TRPs may be interpreted as two TCI states indicated by MAC CE / DCI. [conditions] The "Enhanced TCI States Activation / Deactivation for UE-specific PDSCH MAC CE" is used to specify one or two TCI states for a single code point in the TCI field within the DCI.

[0057] The DCI for common beam indication may be in 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 in a UE-group common DCI format.

[0058] (Multi-TRP PDCCH) To assess the reliability of multi-TRP PDCCHs based on non-single-frequency networks (SFNs), the following considerations 1 to 3 have been examined. [Consideration 1] Encoding / rate matching is based on one repetition, and the same encoded bits are repeated in other repetitions. [Consideration 2] Each iteration has the same number of control channel elements (CCEs), the same encoded 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 decryption.

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

[0060] [Options 1-2] Two sets of PDCCH candidates (within a given search space (SS) set) are associated with two TCI states in the CORESET, respectively. Here, the same CORESET, the same SS set, and PDCCH iterations in 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] Thus, it is being considered that two PDCCH candidates within two SS sets for PDCCH iterations are supported, and that the two SS sets are explicitly linked.

[0065] (SFN PDCCH) For PDCCH / CORESET as defined in Rel.15, one TCI state without a CORESET Pool Index (CORESETPoolIndex) (also known as TRP Info) is set for one CORESET.

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

[0067] Since Rel.17, the following enhancements 1 and 2 regarding PDCCH / CORESET have been considered.

[0068] In cases where multiple antennas (small antennas, transmit / receive points) with the same cell ID form a single frequency network (SFN), up to two TCI states can be set / activated for a single CORESET using upper-layer signaling (RRC signaling / MAC CE) (Enhancement 1). The SFN contributes to at least one of the operation and reliability improvements of the HST (high-speed train).

[0069] Furthermore, in repeated transmissions of PDCCH (which may simply be called "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 a single CORESET, one (at most one) TCI state may be set / activated by upper-layer signaling (RRC signaling / MAC CE).

[0070] If two search space sets are associated with different coresets having different TCI states, this may mean a multi-TRP repetition. If two search space sets are associated with the same coreset (a coreset with the same TCI state), this may mean a single-TRP repetition.

[0071] (HST) In LTE, the placement of HST (high-speed train) antennas in tunnels is challenging. Large antennas transmit both inside and outside the tunnel. For example, the transmission power of a large antenna is around 1 to 5W. 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 around 250mW. Multiple small antennas (transmitting and receiving points) with the same cell ID and a distance of 300m form a single frequency network (SFN). All small antennas within the SFN transmit the same signal on the same PRB at the same time. It is assumed that the terminal transmits and receives to a single base station. In reality, multiple transmitting and receiving points transmit the same DL signal. During high-speed movement, transmitting and receiving points spanning several kilometers form a single cell. Handover occurs when crossing cells. This can reduce the frequency of handovers.

[0072] NR is expected to utilize beams transmitted from a transmission point (e.g., RRH) to communicate with terminals (hereinafter also referred to as UEs) contained within high-speed moving objects such as trains (HSTs). Existing systems (e.g., Rel.15) support the transmission of a unidirectional beam from the RRH to communicate with moving objects (see Figure 1A).

[0073] Figure 1A shows a case where RRHs are installed along the movement path (or direction of movement, direction of travel, or travel path) of a moving object, and a beam is formed from each RRH toward the direction of travel of the moving object. RRHs that form a beam in one direction may also be called unidirectional RRHs. In the example shown in Figure 1A, the moving object receives a negative Doppler shift (-fD) from each RRH.

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

[0075] From Rel.16 onwards, it is anticipated that multiple beams (e.g., two or more) may be transmitted from the RRH. For example, beams may be formed in both the direction of the moving object's movement and the opposite direction (see Figure 1B).

[0076] Figure 1B shows a case where RRHs are installed along the movement path of a moving object, and beams are formed from each RRH both in the direction of the object's movement and in the opposite direction of its movement. An RRH that forms beams in multiple directions (e.g., two directions) may also be called a bidirectional RRH.

[0077] In this HST, the UE communicates in the same way as a single TRP. In base station implementations, transmission can be made from multiple TRPs (same cell ID).

[0078] In the example in Figure 1B, when two RRHs (here, RRH#1 and RRH#2) use SFN, the moving object switches from a signal with a negative Doppler shift to a signal with a positive Doppler shift, which has higher power, midway between the two RRHs. In this case, the maximum Doppler shift change that requires correction is from -fD to +fD, which is twice as large as in the case of a unidirectional RRH.

[0079] In this disclosure, a positive Doppler shift may be interpreted as information relating to a positive Doppler shift, a Doppler shift in the positive direction, or Doppler information in the positive direction. Similarly, a negative Doppler shift may be interpreted as information relating to a negative Doppler shift, a Doppler shift in the negative direction, or Doppler information in the negative direction.

[0080] Here, we compare the following schemes for HST, from Scheme 0 to Scheme 2 (HST Scheme 0 to HST Scheme 2).

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

[0082] In Scheme 0, since the UE receives DL channels / signals with a single TRP equivalent, the TCI state of the PDSCH is 1.

[0083] Furthermore, Rel.16 specifies RRC parameters for distinguishing between transmissions using single TRP and transmissions using SFN. When a UE reports the corresponding UE capability information, it may distinguish between receiving a single TRP DL channel / signal and receiving a PDSCH assuming SFN based on these RRC parameters. On the other hand, a UE may perform transmission and reception using SFN while assuming a single TRP.

[0084] In Scheme 1 of Figure 2B, TRS is 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, the UE receives DL channels / signals from each TRP using the TRS from each TRP, so there are two TCI states for the PDSCH.

[0086] In Scheme 2 of Figure 2C, TRS and DMRS are transmitted specifically by the 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 abrupt changes in Doppler shift and appropriately estimate / compensate for the Doppler shift. Since the DMRS in Scheme 2 is higher 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 upper-layer signaling (RRC information element / MAC CE).

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

[0089] In Scheme 1, two TRS resources are configured for the direction of travel of the HST and its opposite direction.

[0090] In the example in Figure 3A, TRPs (TRP#0, #2, ...) that transmit DL signals in the reverse direction of the HST transmit the first TRS (TRS arriving in front of the HST) on the same time and frequency resource (SFN). TRPs (TRP#1, #3, ...) that transmit DL signals in the direction of the HST transmit the second TRS (TRS arriving behind the HST) on the same time and frequency resource (SFN). The first and second TRSs may be transmitted / received using different frequency resources.

[0091] In the example shown in Figure 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 (equal QCL type D RS). Resource utilization efficiency can be increased by multiplexing the first and second TRS on the same time resources and different frequency resources.

[0093] In the example shown in Figure 4A, RRHs #0-#7 are positioned along the HST's travel path. RRHs #0-#3 and #4-#7 are connected to baseband units (BBUs) #0 and #1, respectively. Each RRH is a bidirectional RRH, forming a beam using each transmission / reception point (TRP) in both the direction of travel and the reverse direction of the travel path.

[0094] In the received signal of the example in Figure 4B (single TRP (SFN) / scheme 1), when the UE receives a signal / channel transmitted from TRP#2n-1 (where n is a non-negative integer) (the beam in the direction of travel of the HST, the beam coming from behind the UE), a negative Doppler shift (in this example, -fD) occurs. Conversely, when the UE receives a signal / channel transmitted from TRP#2n (where n is a non-negative integer) (the beam in the opposite direction of travel of the HST, the beam coming from in front of the UE), a positive Doppler shift (in this example, +fD) occurs.

[0095] Since Rel.17, base stations have been considering implementing Doppler pre-compensation schemes (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) when transmitting downlink (DL) signals / channels from the TRP to the UE via the HST. By performing Doppler compensation in advance when transmitting DL signals / channels to the UE, the TRP can reduce the impact of Doppler shift when receiving DL signals / channels at the UE. In this disclosure, the Doppler pre-compensation scheme may be a combination of Scheme 1 and pre-compensation of Doppler shift by the base station.

[0096] In the Doppler pre-compensation scheme, it is being considered that TRSs from each TRP will be transmitted without Doppler pre-compensation, while PDSCHs from each TRP will be transmitted with Doppler pre-compensation.

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

[0098] In the situation shown in Figure 4C, since the UE receives DL channels / signals from each TRP using the TRS from each TRP, the TCI state of the PDSCH may be two.

[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, using the RRC information element / MAC CE (e.g., Enhanced TCI States Activation / Deactivation for UE-specific PDSCH MAC CE) / DCI (TCI field), one or two TCI states are set / indicated for each TCI code point (code point in the TCI field, DCI code point). When one TCI state is set / indicated, the UE may determine that it is receiving a single TRP PDSCH. Alternatively, when two TCI states are set / indicated, the UE may determine that it is receiving an SFN PDSCH using multiple TRPs.

[0100] (Simultaneous beam updates for multiple CCs) In Rel.16, one MAC CE can update the beam indices (TCI status) of multiple CCs.

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

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

[0103] The PDSCH TCI status activation MAC CE activates the TCI status on all BWP / CCs in the applicable CC list.

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

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

[0106] It has been investigated whether such simultaneous beam updates are applicable only to single TRP cases.

[0107] For PDSCH, UE may follow procedure A below. [Procedure A] The UE receives activation commands to map up to eight TCI states to code points in DCI fields (TCI fields) within a single CC / DL BWP, or within a set of CC / BWPs. When one set of TCI state IDs is activated for a set of CC / DL BWPs, the applicable list of the CC is determined by the CC specified in the activation command, and the same set of TCI states is applied to all DL BWPs within the specified CC. A set of TCI state IDs can only be activated for a set of CC / DL BWPs if the UE does not provide multiple different values ​​for the CORESET Pool Index in the CORESET Information Element (ControlResourceSet) and does not provide at least one TCI code point that maps to two TCI states.

[0108] For PDCCH, UE may be based on the following procedure B. [Procedure B] If the UE provides a simultaneous TCI cell list (simultaneousTCI-CellList) for simultaneous TCI state activation by simultaneous TCI update lists (at least one of simultaneousTCI-UpdateList-r16 and simultaneousTCI-UpdateListSecond-r16), the UE applies the antenna port quasi co-location (QCL) provided by the TCI state having the same activated TCI state ID value to the CORESET having 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 only be provided for simultaneous TCI state activation if the UE does not provide multiple different values ​​for the CORESET pool index (CORESETPoolIndex) in the CORESET information element (ControlResourceSet) and does not provide at least one TCI code point that maps to two TCI states.

[0109] For semi-persistent (SP) / aperiodic (AP)-SRS, UE may be based on the following procedure C. [Step C] When the spatial relation information (spatialRelationInfo) for an SP or AP-SRS resource, set by the SRS resource information element (higher layer parameter SRS-Resource) for a set of CC / BWPs, is activated / updated by MAC CE, the applicable list of the CC is then indicated by the simultaneous spatial update list (higher layer parameter simultaneousSpatial-UpdateList-r16 or simultaneousSpatial-UpdateListSecond-r16), and the spatial relation information is applied to all BWPs within the indicated CC that have the same SRS resource ID for the SP or AP-SRS resource. If the UE does not provide multiple different values ​​for the CORESET Pool Index within the CORESET Information Element (ControlResourceSet) and does not provide at least one TCI code point that maps to two TCI states, then the spatial relation information for an SP or AP-SRS resource set by the SRS resource information element (upper layer parameter SRS-Resource) for one set of CC / BWP will be activated / updated by the MAC CE.

[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 that can have their TCI relationships updated simultaneously using MAC CE. simultaneousTCI-UpdateList1-r16 and simultaneousTCI-UpdateList2-r16 do not contain 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 simultaneously updated using MAC CE. `simultaneousSpatial-UpdatedList1-r16` and `simultaneousSpatial-UpdatedList2-r16` do not contain the same serving cell.

[0112] Here, the concurrent TCI update list and concurrent spatial update list are set by RRC, the CORESET pool index for CORESET is set by RRC, and the TCI code points mapped to TCI states are indicated by MAC CE.

[0113] (Unified / Common TCI Framework) According to the Unified TCI Framework, UL and DL channels can be controlled by a common framework. Rather than defining 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 be applied to all UL channels, and a common beam for DL ​​may be applied to all DL channels.

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

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

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

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

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

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

[0120] In this disclosure, when N=M=X (where X is any integer), it may mean that X TCI states (joint TCI states) common to ULs and DLs (corresponding to X TRPs) are notified / set / instructed to the UE.

[0121] Furthermore, when N=X (where X is any integer) and M=Y (where Y is any integer, and Y=X), it may mean that X UL TCI states (corresponding to X TRPs) and Y DL TCI states (corresponding to Y TRPs) are notified / set / instructed to the UE. These UL TCI states and DL TCI states may represent TCI states common to both UL and DL (i.e., joint TCI states) or separate TCI states for UL and DL (i.e., separate TCI states).

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

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

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

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

[0126] Furthermore, for example, if N=2 and M=1 are specified, it may mean that the UE is notified / set / instructed to have a common TCI state for two ULs and DLs. In this case, the UE may use the two TCI states that are set / instructed as the UL TCI state, and one of the two TCI states that are set / instructed as the DL TCI state.

[0127] Furthermore, for example, if N=2 and M=1 are specified, it may mean that the UE is notified / configured / instructed to have two UL TCI states and one DL TCI state as separate TCI states.

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

[0129] The case M>1 / N>1 may indicate at least one of the following: a TCI status indication for multiple TRPs, and multiple TCI status indications for interband CAs.

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

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

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

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

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

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

[0136] Existing DCI formats 1_1 / 1_2 may be used to indicate common TCI states.

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

[0138] The DCI format indicating the TCI status (DCI format 1_1 / 1_2) may be a DCI format without DL assignment. In this disclosure, the DCI format without DL assignment, the DCI format without scheduling PDSCH (DCI format 1_1 / 1_2), the DCI format that does not include one or more specific fields (DCI format 1_1 / 1_2), the DCI format in which one or more specific fields are set to fixed values ​​(DCI format 1_1 / 1_2), and so on may be interpreted interchangeably.

[0139] For DCI formats without DL assignments (DCI formats that do not include one or more specific fields), the specific field may be any field 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 set), the Transmission Power Control (TPC) command field (for scheduled PUCCHs), the PUCCH resource indicator field, and the PDSCH-to-HARQ feedback timing indicator field (if present). The specific field may be set as a reserved field or ignored.

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

[0141] All RV fields may be set to 1. All MCS fields may be set to 1. All NDI fields may be set to 0. All FDRA fields for type 0 may be set to 0. All FDRA fields for type 1 may be set to 1. All FDRA fields for dynamic switches (upper layer parameter dynamicSwitch) may be set to 0.

[0142] The 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 being considered to represent a single TCI state (M=1, N=1 or M=N=1). In other words, the Rel.17 TCI state is being 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, in the same band where the Rel.17 TCI state is set, it will not be possible to set features (for example, operations using multi-TRP) that utilize the Rel.15 / 16 TCI state / spatial relationship defined in Rel.15 to 17.

[0146] Therefore, it is necessary to extend the common TCI states (Rel.17 TCI states) to support the functionality of Rel.15 / 16 TCI state / spatial relationships, including multi-TRP schemes (for example, to indicate two or more TCI states using MAC CE / DCI).

[0147] For example, in Rel. 18 and later, it is being considered to make the common TCI state applicable to at least one multi-TRP scheme defined in Rel. 16 / 17, as follows: • Single DCI-based NCJT-based PDSCH (Rel. 16). • Multi-DCI based NCJT PDSCH (Rel. 16). • Repetitive transmission of PDSCH using single DCI-based SDM / TDM / FDM (Rel. 16). • Repeated transmission of PDCCH / PUCCH / PUSCH using multiple TRPs (Rel.17). • Operation of multi-TRP in intercells (Rel.17). • Beam management for multi-TRP (Rel.17). HST / SFN (Rel. 17).

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

[0149] However, in the transmission and reception of signals / channels using multi-TRP, the setting, instruction, and application of the common TCI state have not been adequately considered. Insufficient consideration of the setting, instruction, and application methods of the TCI state may lead to a decrease in communication quality, throughput, and other problems.

[0150] Therefore, the inventors have devised a method for appropriately setting / instructing / applying the TCI state, even when applying the TCI state to multiple types of signals / channels in the transmission and reception of signals / channels using multi-TRP.

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

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

[0153] In this disclosure, configure, activate, update, indicate, enable, specify, and select may be interpreted as interchangeable.

[0154] In this disclosure, higher-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof. In this disclosure, RRC, RRC signaling, RRC parameters, higher layer, higher-layer parameters, RRC information elements (IE), RRC messages, and settings may be interpreted as mutually exclusive.

[0155] MAC signaling may use, for example, MAC Control Elements (MAC CEs) or MAC Protocol Data Units (PDUs). In this disclosure, MAC CEs, update commands, and activation / deactivation commands may be interpreted as interchangeable.

[0156] Broadcast information may include, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI, SIB1), and Other System Information (OSI).

[0157] In this 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 in TCI state / QCL assumption, RS of QCL type A in 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 interpreted as each other. In this disclosure, QCL type X-RS, DL-RS associated with QCL type X, DL-RS having QCL type X, DL-RS source, SSB, CSI-RS, and SRS may be interpreted as each other.

[0158] In this disclosure, the terms include: 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 SRS configuration, beam, beam group, precoder, Uplink (UL) transmit entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relationship, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), antenna port (e.g., Demodulation Reference). Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relationship group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) group, PUCCH resource group), 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 (common TCI state)The terms "state," "quasi-co-location (QCL)," and "QCL assumption" may be interchangeable. The UE capability set may include, for example, the maximum number of supported SRS ports.

[0159] The panel may be associated with at least one of the following: a group index for SSB / CSI-RS groups, a group index for group-based beam reporting, or a group index for SSB / CSI-RS groups for group-based beam reporting.

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

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

[0162] In this disclosure, single TRP, single TRP system, single TRP transmission, and single PDSCH may be interpreted interchangeably. In this disclosure, multiple TRP, multi-TRP system, multi-TRP transmission, and multi-PDSCH may be interpreted interchangeably. In this disclosure, single DCI, single PDCCH, multi-TRP based on a single DCI, and activating two TCI states on at least one TCI code point may be interpreted interchangeably.

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

[0164] In this disclosure, multi-TRP, channels using multi-TRP, channels using multiple TCI state / spatial relationships, multi-TRP being enabled by RRC / DCI, multiple TCI state / spatial relationships being enabled by RRC / DCI, and at least one of a single-DCI-based multi-TRP and a multi-DCI-based multi-TRP may be interpreted as mutually exclusive. In this disclosure, multi-DCI-based multi-TRP and a CORESET pool index (CORESETPoolIndex) value of 1 is set for a CORESET may be interpreted as mutually exclusive. In this disclosure, single-DCI-based multi-TRP and at least one code point of a TCI field being mapped to two TCI states may be interpreted as mutually exclusive.

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

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

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

[0168] The QCLs in this disclosure may be interpreted interchangeably with QCL Type D.

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

[0170] In this disclosure, the code points of the DCI field 'Transmission Configuration Indication', the TCI code points, the DCI code points, and the code points of the TCI field may be interpreted as interchangeable.

[0171] In this disclosure, Single TRP and SFN may be interpreted interchangeably. In this disclosure, HST, HST scheme, High-Speed ​​Mobile Scheme, Scheme 1, Scheme 2, NW pre-compensation scheme, HST scheme 1, HST scheme 2, and HST NW pre-compensation scheme may be interpreted interchangeably.

[0172] In this disclosure, a PDSCH / PDCCH utilizing a single TRP may be interpreted as a PDSCH / PDCCH based on a single TRP, or a single TRP PDSCH / PDCCH. Furthermore, in this disclosure, a PDSCH / PDCCH utilizing an SFN may be interpreted as a PDSCH / PDCCH utilizing an SFN in multiple configurations, an SFN-based PDSCH / PDCCH, or an SFN PDSCH / PDCCH.

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

[0174] In this disclosure, the terms HST-SFN scheme, SFN scheme Rel.17 and later, new SFN scheme, new HST-SFN scheme, HST-SFN scenario Rel.17 and 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 at least one of the Doppler pre-compensation schemes may be interpreted as one another.

[0175] In this 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 interpreted interchangeably. In this disclosure, the terms pre-compensation scheme, mitigation scheme, improvement scheme, and correction scheme may be interpreted interchangeably.

[0176] In this disclosure, a linkage-containing PDCCH / searchspace(SS) / CORESET, a linked PDCCH / SS / CORESET, and a pair of PDCCH / SS / CORESETs may be interpreted interchangeably. In this disclosure, a non-linkage-containing PDCCH / SS / CORESET, an unlinked PDCCH / SS / CORESET, and a single PDCCH / SS / CORESET may be interpreted interchangeably.

[0177] In this disclosure, two linked CORESETs for PDCCH iterations and two CORESETs associated with two linked SS sets may be interpreted as one another.

[0178] In this disclosure, SFN-PDCCH repetition, PDCCH repetition, two linked PDCCHs, and one DCI being received across the two linked search spaces (SS) / CORESETs may be interpreted as mutually exclusive.

[0179] In this disclosure, PDCCH repeats, SFN-PDCCH repeats, PDCCH repeats for higher reliability, PDCCH for higher reliability, PDCCH for reliability, and two linked PDCCHs may be interpreted as one another.

[0180] In this disclosure, the terms PDCCH receiving method, PDCCH repetition, SFN-PDCCH repetition, HST-SFN, and HST-SFN scheme may be interpreted interchangeably.

[0181] In this disclosure, the PDSCH receiving method, single DCI-based multi-TRP, and HST-SFN scheme may be interpreted as interchangeable.

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

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

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

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

[0186] In each embodiment of this disclosure, SFN PDSCH / PDCCH may be interpreted as equivalent to SFN PDSCH / PDCCH as defined in Rel. 17 and later.

[0187] In each embodiment of this disclosure, the use of multiple TRPs based on multi-DCI may mean that the CORESET pool index = 1 is set. Alternatively, the use of multiple TRPs based on multi-DCI may mean that the CORESET pool index has two different values ​​(e.g., 0 and 1).

[0188] In each embodiment of this disclosure, UL transmission using multiple panels may mean a UL transmission scheme using multiple panels of UE by DCI enhancement.

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

[0190] Each embodiment of the present disclosure described below may be applied to the transmission and reception of any channel / signal to which the Unified TCI State Framework defined above in Rel. 17 and later applies.

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

[0192] In this disclosure, the terms small, few, short, and low may be interpreted interchangeably. Similarly, in this disclosure, terms such as ignore and drop may be interpreted interchangeably.

[0193] In this disclosure, "highest" and "lowest" may be interpreted interchangeably. Also, in this disclosure, "highest" may be interpreted interchangeably with "nth (where n is any natural number) largest," "greater than," "higher than," etc. Also, in this disclosure, "lowest" may be interpreted interchangeably with "nth (where n is any natural number) smallest," "smaller than," "lower than," etc.

[0194] In this disclosure, repetition, repeated transmission, and repeated reception may be interpreted as mutually exclusive.

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

[0196] In this disclosure, a first TRP may correspond to a first TCI state. In this disclosure, a second TRP may correspond to a second TCI state. In this disclosure, an nth TRP may correspond to an nth TCI state.

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

[0198] In the embodiments of this disclosure described below, the application of multiple TCI states in transmission and reception using multiple TRPs will mainly be described using a method targeting two TRPs. However, the number of TRPs may be three or more, and each embodiment may be applied in accordance with the number of TRPs.

[0199] (Wireless communication method) <Embodiment 0> A single DCI-based multi-TRP may be assumed to be supported when the multi-TRP utilizes an ideal backhaul (see Figure 7A).

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

[0201] In this disclosure, one TCI state may mean one joint (DL / UL) TCI state, or 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 multiple TRPs utilize ideal backhaul / non-ideal backhaul (see Figure 7B).

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

[0204] The ideal backhaul may also 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 also 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 state included in the DCI (TCI field) may follow at least one of the following options 0-1 and 0-2.

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

[0207] [Options 0-2] The TCI fields defined up to Rel. 15 / 16 may be extended (see Figure 8B). For example, a DCI may contain multiple TCI fields (e.g., two). The number of bits in each TCI field may be a specific number (e.g., 3).

[0208] In options 0-2, DCI without DL assignments does not incur additional DCI overhead. On the other hand, DCI with DL assignments incurs additional DCI overhead.

[0209] For a single DCI-based multi-TRP, in the case of a joint TCI state, the DL / UL (joint) TCI state may be activated to the UE using MAC CE. The UE may then use DCI (beam indication) to indicate the first DL / UL (joint) TCI state and the second DL / UL (joint) TCI state (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 Figure 9B).

[0211] In the example shown in Figure 9B, all TCI code points corresponding to the active TCI state correspond to two TCI states. However, 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 a single DCI-based multi-TRP, in the case of a separate TCI state, the DL (separate) TCI state and UL (separate) TCI state may be activated to the UE using MAC CE. The UE may then use DCI (beam indication) to specify 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 (see Figure 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). However, associations may be used such that at least one TCI code point corresponding to the active TCI state corresponds to two TCI states. By using such associations, it is possible to dynamically switch between single TRP and multi-TRP.

[0215] In Figure 10A, an example is shown where separate TCI states are activated for the DL TCI state and the UL TCI state by MAC CE. However, even in the case of separate TCI states, the activated DL TCI state and UL TCI state may include a common TCI state.

[0216] For multi-DCI based multi-TRP, at least one of the following may be performed for each CORESET pool index: setting the TCI status by RRC, activation by MAC CE, and instruction by DCI.

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

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

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

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

[0221] When the DCI corresponding to each CORESET pool index indicates 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 a single TCI state has been indicated. In this case, the UE may perform an operation using a single TRP.

[0222] Although the above explanation of multi-DCI-based multi-TRP was based on an example using a joint TCI state, it can also be appropriately applied to cases using a separate TCI state.

[0223] In this disclosure, the indicated TCI state, Rel.17 TCI state, common TCI state, and unified TCI state may be interpreted as mutually exclusive. In this disclosure, the common TCI state, Rel.17 TCI state, and Rel.18 TCI state applied to channels / signals utilizing multiple TRPs may be interpreted as mutually exclusive.

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

[0225] The specific channel / signal may be a UE-specific (dedicated) DL channel / signal. The UE-specific DL channel / signal 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. The specific UL channel / signal may be at least one of the following: a PUSCH indicated by DCI (indicated by dynamic grant), a configured grant PUSCH, multiple (all) unique PUCCHs (resources), or an SRS (e.g., an aperiodic (A-)) SRS).

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

[0228] <First Embodiment> In the first embodiment, the application of TCI states and the number of TCI states 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 N TCI states (joint TCI states, separate (DL / UL) TCI states) to the DL / UL channels / signals.

[0230] The UE may set / indicate up to M and N TCI states (joint TCI states, separate (DL / UL) TCI states) at least one of these (for example, M and N being numbers of 2 or more).

[0231] In this case, the UE may be configured with channels / RS / resources / resource sets corresponding to the TRP index.

[0232] The indexes relating to the TRP may be interpreted as the TRP index, CORESET pool index, (UE) panel index, and UE Capability Set index, respectively.

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

[0234] In a single DCI-based multi-TRP, the first and second indexes of the TRP may be interpreted as the first and second set IDs and the first and second TCI states, respectively.

[0235] In a multi-DCI-based multi-TRP, the first and second indexes of the index relating to the TRP may be interpreted as the CORESET pool index of the first and second values.

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

[0237] The setting / instruction may be set / instructed, for example, in a scenario utilizing inter-cell multi-TRP. The setting / instruction may also be based on the reporting of corresponding UE capability information. In this case, the source RS of the TCI state may be an RS (e.g., SSB) associated with a PCI different from the physical cell index (PCI) of the serving cell (an additional PCI). Whether or not the source RS of such an additional PCI-related SSB can be applied to the UL TCI state (e.g., N) may be set independently by the UE.

[0238] The UE may set / instruct a PCI value directly, or it may set / instruct a PCI value that has been re-indexed within the PCI list being set.

[0239] 《Aspect 1-1》 Embodiment 1-1 describes the maximum number of TCI states that can be set for a UE.

[0240] UE may apply at least one of M DL TCI states and N UL TCI states (or M (N, M=N) joint TCI states). M and N may be 2 or 3 or more.

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

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

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

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

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

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

[0247] For cases where (M,N)>1, the number of TCI states that can be set / activated for joint / separate TCI states may be limited to a specific number.

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

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

[0250] Note that the number of configured / activated TCI states in this aspect may be determined for each BWP (configuration).

[0251] 《Aspect 1-2》 In Aspect 1-2, the list of CC / BWPs configured for the UE will be described.

[0252] In CA in the unified TCI framework of Rel.17, it is being considered to support a CC-specific TCI state pool / configuration (Case 1) and a CC-common TCI state pool / configuration (Case 2).

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

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

[0255] The UE may refer to the TCI state pool configured for another specific BWP / CC (reference BWP / CC) for determining the TCI state of a BWP / CC for which no TCI state pool is configured.

[0256] The UE may refer to the TCI state pool according to at least one of the following Aspects 1-2-A and 1-2-B.

[0257] In the aspects described below, "CC" is mainly described, but "CC" may be appropriately read as "BWP".

[0258] [Aspect 1-2-A] The UE may set a CC list including a plurality of CCs using upper layer signaling (RRC signaling).

[0259] For determining the TCI state of a CC for which no TCI state pool is set, the UE may determine a CC (reference BWP / CC) for which a TCI state pool is set among the plurality of CCs. The UE may determine / update / apply the TCI state of a CC for which no TCI state pool is set by referring to the TCI state pool set for the determined CC.

[0260] The CC list may be used for setting the TCI state pool in the above Case 2. The CC list may be used for updating / indicating 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] The UE may set a CC list including a plurality of CCs using upper layer signaling (RRC signaling).

[0263] The UE may set a first CC list used for updating / indicating the (unified) TCI state (ID) using MAC CE / DCI.

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

[0265] The UE may be configured with a second CC list, which is used to configure the TCI state pool in Case 2 above.

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

[0267] The second CC list may have a specific number set for each cell / cell group. This specific number may be, for example, up to four. This specific number may be determined based on the reported UE capability information.

[0268] Figure 14 shows an example of the CC list settings related to Embodiment 1-2-B. Figure 14 shows Case 1 described above. In the example shown in Figure 14, a TCI state pool (list) is set for each of CC#1 (BWP#1 in CC#1), CC#2 (BWP#1 in CC#3), and CC#3 (BWP#1 in CC#3). This TCI state list is set within the PDSCH settings.

[0269] In the example shown in Figure 14, a first CC list is set for the UE, which is used to update / instruct the (unified) TCI status (ID) using MAC CE / DCI. This first CC list includes a list (first CC list #1) containing CC#1 (in which BWP#1) and CC#2 (in which BWP#1), and a list (first CC list #2) containing CC#3 (in which BWP#1).

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

[0271] Note that the first CC list may have multiple entries. Figure 14 shows an example where the first CC list has multiple entries.

[0272] Furthermore, the TCI status IDs in CC#1 (and BWP#1 in CC#2) and CC#2 (and BWP#1 in CC#3) may be specified using separate MAC CE / DCIs, or they may be specified using a common MAC CE / DCI.

[0273] Figure 15 shows another example of the CC list configuration according to Embodiment 1-2-B. Figure 15 shows Case 2 described above. In the example shown in Figure 15, a TCI state pool (list) is set for CC#1 (BWP#1 in CC#1), but no TCI state pool (list) is set for CC#2 (BWP#1 in CC#2) and CC#3 (BWP#1 in CC#3). The TCI state list is set within the PDSCH configuration.

[0274] In the example shown in Figure 15, a first CC list is set for the UE, which is used to update / instruct the (unified) TCI status (ID) using MAC CE / DCI (indicating multiple CCs / BWPs using a common MAC CE / DCI). This first CC list includes a list containing CC#1 (and BWP#1 in it) and CC#2 (and BWP#1 in it) (first CC list #1), and a list containing CC#3 (and BWP#1 in it) (first CC list #2).

[0275] In the example shown in FIG. 15, a second CC list (indicating a plurality of CCs / BWPs that use a common TCI state pool) used for setting the TCI state pool in Case 2 above is set for the UE. The UE refers to the TCI state list set for a specific CC among the plurality of CCs included in the second CC list. In the example shown in FIG. 15, the second CC list includes CC#1 (BWP#1 therein), CC#2 (BWP#1 therein), and CC#3 (BWP#1 therein).

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

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

[0278] Note that in the example shown in FIG. 15, an example is shown where the first CC list and the second CC list indicate different CCs (that is, include different combinations of CCs), but it is not limited to this. The first CC list and the second CC list may be lists indicating the same CC.

[0279] Furthermore, at least one of the first CC list and the second CC list may have multiple entries. The example shown in Figure 15 illustrates a case where the first CC list has multiple entries and the second CC list has one entry.

[0280] Furthermore, the TCI status IDs in CC#1 (and BWP#1 in CC#2) and CC#2 (and BWP#1 in CC#3) may be specified using separate MAC CE / DCIs, or they may be specified using a common MAC CE / DCI.

[0281] Furthermore, if multiple first CC lists are set, and a TCI status (ID) is indicated using MAC CE / DCI for at least one CC / BWP included in one of the multiple lists, the UE may apply the indicated TCI status (ID) to multiple (e.g., all) CC / BWPs included in that list. The UE may also apply the TCI status separately for each of the multiple lists.

[0282] If a first CC list is set up that covers all CCs / BWPs, the UE may determine / assume / expect that a TCI status (ID) will be indicated for each CC / BWP using MAC CE / DCI.

[0283] Different CC lists do not need to contain the same CC / BWP.

[0284] The same CC list may contain BWP / CCs corresponding to different settings / instructions. These different settings / instructions may, for example, be settings / instructions for (M,N)=1 (settings / instructions defined in Rel.17) and settings / instructions for (M,N)>1 (settings / instructions defined in Rel.18 and later).

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

[0286] The same CC list may include BWP / CCs corresponding to different TCI state modes. These TCI state modes may be, for example, either joint TCI state mode or separate TCI state mode.

[0287] All BWP / CCs included in the same CC list may correspond to the same TCI state mode. This TCI state mode may be, for example, either the joint TCI state mode or the separate TCI state mode.

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

[0289] Additionally, existing / new / common / separate CC lists for at least one of M and N TCI state IDs may be updated / activated for the UE.

[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 determine the number of TCI states to be appropriately applied, set / activated.

[0291] <Second Embodiment> In the second embodiment, the application of the indicated TCI state will be described.

[0292] The UE may indicate 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.17TCI state) with multiple DL / UL channels / signals.

[0294] The DL / UL channel / signal may be at least two channel / RS as described in the first embodiment above.

[0295] The UE may conform to at least one of the following embodiments 2-1 to 2-4. The following description mainly concerns an example with two indicated TCI states, but the number of indicated TCI states may be greater than two.

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

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

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

[0299] If an RRC parameter is set that instructs the system to follow two designated TCI states in Rel.18 (e.g., followTwoUnifiedTCI-State-r18), the UE may determine that two TCI states are designated and that both of those designated TCI states should be applied.

[0300] Furthermore, the RRC parameter "followTwoUnifiedTCI-State-r18" may represent one of the following values: applying the first of the two indicated TCI states (e.g., "first / 1st"), applying the second of the two indicated TCI states (e.g., "second / 2nd"), or 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 set to follow the first of the two indicated TCI states (e.g., "follow1stUnifiedTCI-State-r18"), follow the second of the two indicated TCI states (e.g., "follow2ndUnifiedTCI-State-r18"), or follow 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 the DL / UL channel / RS (DL / UL channel / RS).

[0303] The DL / UL channel / RS may be at least one of the following: PDSCH using multi-TRP, repetition of PDSCH / PDCCH / PUSCH / PUCCH using multi-TRP, SFN PDCCH / PDSCH, or SRS (resource set) with a codebook (CB) / non-codebook (NCB) usage.

[0304] The UE may determine, based on specific rules, which of the indicated TCI states to apply.

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

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

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

[0308] 《Aspect 2-2》 The UE may apply one of the two indicated TCI states to the DL / UL channel / RS (DL / UL channel / RS).

[0309] The DL / UL channel / RS may be at least one of the following: PDSCH without multi-TRP, repetition of PDSCH / PDCCH / PUSCH / PUCCH without multi-TRP, PDCCH / PDSCH without SFN scheme, or CSI-RS.

[0310] The UE may determine which of the indicated TCI states to apply based on certain rules. These specific rules may be at least one of the following embodiments 2-2-A to 2-2-C.

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

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

[0313] The UE may decide which of the first or second TCI conditions it has determined to apply.

[0314] [Aspect 2-2-B] The UE may decide to apply a specific TCI state from among the two indicated TCI states.

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

[0316] [Aspect 2-2-C] The UE may use higher-layer signaling (RRC / MAC CE) to determine which of the two indicated TCI states to apply.

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

[0318] Figure 16 shows an example of TCI state determination according to embodiment 2-1 / 2-2. In the example shown in Figure 16, the UE is given two CORESET settings: one corresponding to CORESET#1 and another corresponding to CORESET#2. The setting corresponding to CORESET#1 includes followUnifiedTCI-State-r17 and a parameter for setting SFN scheme A (SFN scheme A), while the setting corresponding to CORESET#2 includes followUnifiedTCI-State-r17. The UE is also instructed to have two TCI states (TCI#1 and TCI#2).

[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 decides to apply the two indicated TCI states (TCI#1 and TCI#2). The UE also determines that for CORESET#2, it will apply a specific TCI state (TCI#1 in the example in Figure 16) from the two indicated TCI states.

[0320] In the example shown in Figure 16, the decision to apply the TCI state based on the CORESET setting is demonstrated, but this can also be appropriately applied to the settings of other specific DL / UL channels / RS / resources (for example, the DL / UL channels / RS described in the first embodiment above).

[0321] 《Aspect 2-3》 The UE may decide not to apply the two indicated TCI states (common TCI states) to multiple (e.g., all) DL / UL channels / RS (DL / UL channel / RS) to which the indicated TCI states (common TCI states) are applicable.

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

[0323] The DL / UL channel / RS may be at least two of the DL / UL channels / RS described in the first embodiment above.

[0324] For channels / RSs where multiple (two) TCI states can be applied, the UE may be configured to apply multiple (two) indicated TCI states. This configuration may be done, 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 at least one of the following: PDSCH using multi-TRP, repetition of PDSCH / PDCCH / PUSCH / PUCCH using multi-TRP, SFN PDCCH / PDSCH, or an SRS (resource set) with a codebook (CB) / non-codebook (NCB) usage.

[0326] The UE may be configured to apply one specified TCI state for channels / RSs where only one TCI state can be applied. This configuration may be done, for example, using the RRC parameter "followUnifiedTCI-State-r17".

[0327] The channel / RS to which the single TCI state can be applied may be, for example, at least one of the following: PDSCH without multi-TRP, repetition of PDSCH / PDCCH / PUSCH / PUCCH without multi-TRP, PDCCH / PDSCH without SFN scheme, or CSI-RS.

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

[0329] Furthermore, the UE does not need to assume or expect that, in different CORESET settings, there will be separate parameters indicating the application of multiple (two) specified TCI states and parameters indicating the application of a single specified TCI state.

[0330] In this case, the UE may decide which of the two indicated TCI states to apply according to at least one of embodiments 2-2-A to 2-2-C above. Alternatively, the UE may decide which of the two indicated TCI states to apply according to embodiment 2-4 below.

[0331] Figure 17 shows an example of TCI state determination according to embodiment 2-3. In the example shown in Figure 17, the UE is given two CORESET settings: one corresponding to CORESET#1 and another corresponding to CORESET#2. The setting corresponding to CORESET#1 includes followTwoUnifiedTCI-State-r18 and a parameter for setting SFN scheme A (SFN scheme A), while the setting corresponding to CORESET#2 includes followUnifiedTCI-State-r17. The UE is also instructed to have two TCI states (TCI#1 and TCI#2).

[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 decides to apply the two indicated TCI states (TCI#1 and TCI#2). The UE also determines that neither of the two indicated TCI states should be applied to CORESET#2. In this case, the application of the already applied / indicated TCI state (TCI#5 in Figure 17) is maintained, and no TCI state updates are performed.

[0333] In the example shown in Figure 17, the decision to apply the TCI state based on the CORESET setting is demonstrated, but this can also be appropriately applied to the settings of other specific DL / UL channels / RS / resources (for example, the DL / UL channels / RS described in the first embodiment above).

[0334] 《Appearance 2-4》 The UE may have an RRC parameter set to indicate which of the two indicated TCI states to apply, or whether to apply both.

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

[0336] The RRC parameter may represent one of the following: 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 determine the TCI state by applying the RRC parameters.

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

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

[0340] For example, if the RRC parameter indicates both the first and second TCI states, the UE may decide to apply both of the indicated TCI states.

[0341] Figure 18 shows an example of TCI state determination according to embodiment 2-4. In the example shown in Figure 18, the UE is given two CORESET settings: one corresponding to CORESET#1 and another corresponding to CORESET#2. The setting corresponding to CORESET#1 includes followBothUnifiedTCI-State-r18 and a parameter for setting SFN scheme A (SFN scheme A), while the setting corresponding to CORESET#2 includes follow2ndUnifiedTCI-State-r18. The UE is also instructed to have two TCI states (TCI#1 and TCI#2).

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

[0343] Furthermore, the UE determines that one TCI state (TCI#2 in Figure 18) should be applied to CORESET#2 based on the instruction of follow2ndUnifiedTCI-State-r18 included in the CORESET#2 configuration. In this case, "follow2ndUnifiedTCI-State-r18" may be a parameter indicating the application of a second TCI state.

[0344] In the example shown in Figure 18, the decision to apply the TCI state based on the CORESET setting is demonstrated, but this can also be appropriately applied to the settings of specific DL / UL channels / RS / resources other than CORESET (for example, the DL / UL channels / RS described in the first embodiment above).

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

[0346] <Third Embodiment> Rel.16 supports both joint ACK / NACK (HARQ-ACK) feedback (mode) and separate ACK / NACK (HARQ-ACK) feedback (mode).

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

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

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

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

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

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

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

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

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

[0356] 《Aspect 3-1》 For each TRP / TCI state, a PUCCH resource / PUCCH resource set / PUCCH configuration (PUCCH-Config) may be set for the UE.

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

[0358] Figure 20 shows an example of how to configure PUCCH resources according to embodiment 3-1. In the example shown in Figure 20, the UE is configured with a PUCCH resource set corresponding to the first TRP / TCI state and a PUCCH resource set corresponding to the second TRP / TCI state.

[0359] Up to a first number (e.g., 4) of PUCCH resource sets can be configured for each TRP / TCI state. Up to a second number (e.g., 8) of PUCCH resources can be configured within each PUCCH resource set. 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 in the UCI is N0 (e.g., 2) or less, the UE decides to use the first PUCCH resource set. Also in the example shown in Figure 20, if the number of bits in the UCI is greater than N0 and N1 or less, the UE decides to use the second PUCCH resource set.

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

[0361] Furthermore, for the settings for each TRP / TCI state, the PUCCH resource set setting corresponding to the first (or second) TRP / TCI state may use the PUCCH resource set setting defined in existing specifications (e.g., Rel. 15-17). Alternatively, for the settings for each TRP / TCI state, the PUCCH resource set setting corresponding to the first (or second) TRP / TCI state may use the PUCCH resource set setting newly defined (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 the PUCCH resource set that is newly defined (for example, in Rel. 18 or later).

[0363] 《Aspect 3-2》 A common PUCCH resource / PUCCH resource set / PUCCH configuration (PUCCH-Config) may be set for each TRP / TCI state in the UE.

[0364] A single PUCCH resource may be associated with a single TRP / TCI state. The UE may be directed to a PUCCH resource associated with a single TRP / TCI state. A TRP / TCI state may be associated independently with each PUCCH resource.

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

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

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

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

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

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

[0371] Figure 21 shows an example of how to configure PUCCH resources according to embodiment 3-2. In the example shown in Figure 21, 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 in the example shown in Figure 20.

[0372] In the example shown in Figure 21, the UE determines the PUCCH resources corresponding to each TRP / TCI state 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) from "000" to "011" are associated with the first TRP / TCI state, and PUCCH resources with PRIs from "100" to "111" are associated with the second TRP / TCI state. Based on these associations, the UE determines the PUCCH resources associated with each TRP / TCI state.

[0373] For settings common to all TRP / TCI states, the PUCCH resource set settings defined in existing specifications (e.g., Rel. 15-17) may be used. Alternatively, for settings common to all TRP / TCI states, the PUCCH resource set settings newly defined (e.g., in Rel. 18 or later) may be used.

[0374] According to embodiment 3-2, the joint TCI state / separate (UL) TCI state of a PUCCH resource can be indicated by using the selection of a PUCCH resource using a PRI / control channel element (CCE) index.

[0375] Modification 1 of Embodiment 3-2 A common PUCCH resource / PUCCH resource set / PUCCH configuration (PUCCH-Config) may be set for each TRP / TCI state in the UE.

[0376] A single PUCCH resource may be associated with one or more (two) TRP / TCI states. The UE may indicate a PUCCH resource associated with one or more (two) TRP / TCI states.

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

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

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

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

[0381] Figure 22 shows an example of a method for setting PUCCH resources according to Modification 1 of Embodiment 3-2. In the example shown in Figure 22, a PUCCH resource set common to each TRP / TCI state is set for the UE. The setting of the PUCCH resource set and PUCCH resources is the same as in the example shown in Figure 20.

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

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

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

[0385] For settings common to all TRP / TCI states, the PUCCH resource set settings defined in existing specifications (e.g., Rel. 15-17) may be used. Alternatively, for settings common to all TRP / TCI states, the PUCCH resource set settings newly defined (e.g., in Rel. 18 or later) may be used.

[0386] According to Modification 1 of Embodiment 3-2, the joint TCI state / separate (UL) TCI state of a PUCCH resource can be specified using RRC / MAC CE / DCI / specific rules.

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

[0388] Modification 2 of Embodiment 3-2 A common PUCCH resource / PUCCH resource set / PUCCH configuration (PUCCH-Config) may be set for each TRP / TCI state in the UE.

[0389] A single PUCCH resource may be associated with one or more (two) TRP / TCI states. The UE may indicate a PUCCH resource associated with one or more (two) TRP / TCI states.

[0390] According to Modification 2 of Embodiment 3-2, the joint TCI state / separate (UL) TCI state of a PUCCH resource can be specified using RRC / MAC CE / DCI / specific rules.

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

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

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

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

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

[0396] Figure 23 shows an example of a method for setting PUCCH resources according to Modification 2 of Embodiment 3-2. In the example shown in Figure 23, a PUCCH resource set common to each TRP / TCI state is set for the UE. The setting of the PUCCH resource set and PUCCH resources is the same as in the example shown in Figure 20.

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

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

[0399] For settings common to all TRP / TCI states, the PUCCH resource set settings defined in existing specifications (e.g., Rel. 15-17) may be used. Alternatively, for settings common to all TRP / TCI states, the PUCCH resource set settings newly defined (e.g., in Rel. 18 or later) may be used.

[0400] According to the third embodiment described above, even when using multiple TRPs and a common TCI state is indicated, the PUCCH resource can be appropriately determined.

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

[0402] Furthermore, the third embodiment may be applied when joint / separate ACK / NACK feedback is configured in a multi-DCI-based multi-TRP. In a single-DCI-based multi-TRP, if the network (base station) wants to update the joint TCI state / separate (UL) TCI state of 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.

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

[0404] Furthermore, the third embodiment may be applied when specific upper-layer parameters are set. In other words, the third embodiment may also be applied in cases where a single TRP is set.

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

[0406] In each embodiment / aspect / option of this disclosure, TRP-specific (additional) Transmitted Precoding Matrix Indicator (TPMI) fields / SRI fields may be used for PUSCH using multi-TRP in Rel. 17.

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

[0408] A UE that has the corresponding higher-layer parameter (the parameter that enables the function) set may perform that function. It may also be stipulated that "a UE for which the corresponding higher-layer parameter is not set shall not perform that function (for example, in accordance with Rel. 15 / 16)."

[0409] A UE that reports its ability to support a particular function may perform that function. It may also be stipulated that "a UE that does not report its ability to support a particular function shall not perform that function (for example, in accordance with Rel. 15 / 16)."

[0410] If the UE reports its capability to support the function and the corresponding higher-layer parameters are set, the UE may perform the function. It may also be stipulated that "if the UE does not report its capability to support the function, or if the corresponding higher-layer parameters are not set, the UE shall not perform the function (e.g., according to Rel. 15 / 16)."

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

[0412] The function may also involve applying common / unified TCI status.

[0413] The function may also involve the application of joint DL / UL TCI status.

[0414] The function may also involve applying the separate DL / UL TCI state.

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

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

[0417] UE capability may be defined by whether or not it supports a joint DL / UL TCI state (mode) with M=2 and N=1.

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

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

[0420] UE capability may be defined by whether or not it supports a separate DL / UL TCI state with M=1 and N=2.

[0421] UE capability may be defined by whether or not it supports a separate DL / UL TCI state with M=2 and N=1.

[0422] UE capability may be defined by whether or not it supports a separate DL / UL TCI state with M=2 and N=2.

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

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

[0425] UE capability may be defined by whether or not it supports common TCI states for single DCI-based multi-TRP.

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

[0427] UE capability may be defined by whether or not it supports common TCI states for single DCI-based multi-TRP and common TCI states 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 and at least one of the methods described in the fourth embodiment.

[0429] UE capability may be defined by whether or not it supports separate BATs in different TRPs (CORESET pool indexes).

[0430] According to the other embodiments described above, 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 one embodiment of this disclosure will be described below. In this wireless communication system, communication is performed using any or a combination thereof of the wireless communication methods according to the above embodiments of this disclosure.

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

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

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

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

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

[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 (CC) and Dual Connectivity (DC).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[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 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 SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. SS, SSB, etc., may also be called reference signals.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0472] The transmission path interface 140 may send and receive signals (backhaul signaling) with 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] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0474] The transmitting / receiving unit 120 may transmit instruction information for multiple transmit setting instruction (TCI) states (multiple common TCI states) that are applied to multiple signals (channel / RS). The control unit 110 may use the instruction information to instruct that each of the multiple TCI states be applied to signals that utilize multiple transmit / receive points (multiple TRPs). Each of the multiple TCI states may be a TCI state that is applied to both downlink (DL) signals and uplink (UL) signals (joint TCI state), or a TCI state that is applied to DL signals and a TCI state that is applied to UL signals (separate TCI state) (first and second embodiments).

[0475] The transmitting / receiving unit 120 may transmit setting information (e.g., PUCCH setting / PUCCH resource set setting) relating to one or more transmit setting instruction (TCI) states. The control unit 110 may use the setting information to specify the PUCCH resource corresponding to each TCI state (third embodiment).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0493] The transmitting / receiving unit 220 may receive instruction information for multiple transmit setting instruction (TCI) states (multiple common TCI states) applied to multiple signals (channel / RS). Based on the instruction information, the control unit 210 may apply the multiple TCI states to signals that utilize multiple transmit / receive points (multiple TRPs). Each of the multiple TCI states may be a TCI state applied to both downlink (DL) signals and uplink (UL) signals (joint TCI state), or a TCI state applied to DL signals and a TCI state applied to UL signals (separate TCI state) (first and second embodiments).

[0494] The transmitting / receiving unit 220 may receive a list of cells (first / second list) to which the instruction information is to be applied. Different lists do not have to contain the same cells (first embodiment).

[0495] The control unit 210 may decide to apply one of the multiple TCI states to signals other than those using the multiple transmission and reception points (for example, a channel / RS using the Niitsuru TRP) (second embodiment).

[0496] The transmitting / receiving unit 220 may receive at least one of the following: first setting information (e.g., followUnifiedTCI-State-r17 / follow1stUnifiedTCI-State-r18 / follow2ndUnifiedTCI-State-r18) which sets the application of one of the plurality of TCI states, and second setting information (e.g., followTwoUnifiedTCI-State-r18 / followBothUnifiedTCI-State-r18) which sets the application of the plurality of TCI states. The control unit 210 may control the 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 transmitting / receiving unit 220 may receive configuration information (e.g., PUCCH settings / PUCCH resource set settings) relating to a physical uplink control channel (PUCCH) resource set corresponding to one or more transmit setting instruction (TCI) states (TRPs). The control unit 210 may determine the PUCCH resource corresponding to each TCI state based on the configuration information (third embodiment).

[0498] The aforementioned configuration information may be the configuration of a PUCCH resource set corresponding to a single TCI state (TRP). The transmitting / receiving unit 220 may receive multiple pieces of the aforementioned configuration information (third embodiment).

[0499] The aforementioned configuration information may also be a setting for a PUCCH resource set common to multiple TCI states (TRPs) (third embodiment).

[0500] The transmitting / receiving unit 220 may receive information (flags / indicators) regarding the association between the PUCCH resource included in the setting information and the index of the TCI state.

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

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

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

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

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

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

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

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

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

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

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

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

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

[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), and a field programmable gate array (FPGA), and some or all of each functional block may be implemented using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[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. At least one of the base station and the mobile station may also be a device mounted on a moving object, the moving object itself, etc.

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

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

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

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

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

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

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

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

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

[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 sends and receives data (information) via the communication port 63 to the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58 provided in the vehicle 40.

[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 external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. The communication module 60 may also be, for example, the base station 10 or the user terminal 20 described above (it may function as the base station 10 or the user terminal 20).

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

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

[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, axle 48, various sensors 50-58, etc., which are provided in the vehicle 40.

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

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

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

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

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

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

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

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

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

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

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

[0578] The term "maximum transmit power" as used in this disclosure may mean the maximum 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,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

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

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

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

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

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

Claims

1. A receiving unit that receives setting information relating to a physical uplink control channel (PUCCH) resource set corresponding to a plurality of transmission setting instruction (TCI) states, and information indicating the TCI state associated with a PUCCH resource included in the PUCCH resource set, A terminal having a control unit that determines, based on the setting information and the information indicating the TCI state, to apply the plurality of TCI states to one or more specific PUCCH resources, and determines to apply any one of the plurality of TCI states to PUCCH resources other than the one or more specific PUCCH resources.

2. The terminal according to claim 1, wherein the one or more specific PUCCH resources to which the plurality of TCI states are applied are used for at least one of repeated transmission of PUCCH to a plurality of transmit / receive points (TRPs) and simultaneous transmission of PUCCH using a plurality of panels.

3. A step of receiving: setting information relating to a set of physical uplink control channels (PUCCH) resources corresponding to a plurality of transmit setting instruction (TCI) states, and information indicating a TCI state associated with a PUCCH resource included in the PUCCH resource set. A wireless communication method for a terminal, comprising the steps of determining, based on the setting information and the information indicating the TCI state, to apply the plurality of TCI states to one or more specific PUCCH resources, and determining to apply any one of the plurality of TCI states to PUCCH resources other than the one or more specific PUCCH resources.

4. A transmission unit that transmits setting information relating to a physical uplink control channel (PUCCH) resource set corresponding to a plurality of transmission setting instruction (TCI) states, and information indicating the TCI state associated with a PUCCH resource included in the PUCCH resource set, A base station having a control unit that, using the setting information and the information indicating the TCI state, instructs the application of the plurality of TCI states to one or more specific PUCCH resources, and instructs the application of any one of the plurality of TCI states to PUCCH resources other than the one or more specific PUCCH resources.

5. A system having a terminal and a base station, The terminal includes a receiving unit that receives configuration information relating to a physical uplink control channel (PUCCH) resource set corresponding to a plurality of transmission configuration instruction (TCI) states, and information indicating the TCI state associated with a PUCCH resource included in the PUCCH resource set. The system includes a control unit that determines, based on the setting information and the information indicating the TCI state, to apply the plurality of TCI states to one or more specific PUCCH resources, and determines to apply any one of the plurality of TCI states to PUCCH resources other than the one or more specific PUCCH resources, The base station includes a transmitting unit that transmits the setting information and information indicating the TCI status, A system comprising: a control unit that, using the setting information and the information indicating the TCI state, instructs the application of the plurality of TCI states to one or more specific PUCCH resources, and instructs the application of any one of the TCI states to PUCCH resources other than the one or more specific PUCCH resources.

Images