Terminal, wireless communication method, base station and system

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives a downlink control channel to which repeated transmission or single frequency network transmission is applied; and a control unit that determines configuration information of the downlink control channel on the basis of whether or not there are schedule settings or support for a plurality of downlink shared channels at a plurality of transmission / reception points using downlink control information which is provided by the downlink control channel.

Description

[Technical Field]

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

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

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

[0004] [Non-Patent Document 1] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the Invention [Problem to be solved by the invention]

[0005] In future wireless communication systems (e.g., NR), it is being considered that one or more transmission / reception points (TRPs) (multi-TRPs) will use one or more panels (multi-panels) to perform DL transmission (e.g., downlink shared channel (e.g., PDSCH) transmission) to a terminal (user terminal, User Equipment (UE)).

[0006] In addition, in NR, it is also assumed that multiple signals / channels (e.g., multi-PDSCH) are transmitted / received from one or more transmission / reception points. For example, it is conceivable that multi-PDSCH transmission is controlled using one or more downlink control information (e.g., DCI) / downlink control channels (e.g., PDCCH) from one or more transmission / reception points.

[0007] However, in the current NR specifications, there has been insufficient consideration of how to control multiple DL transmissions from one or more TRPs.

[0008] Therefore, the present disclosure provides a terminal and a wireless communication method that can appropriately perform communication even when multiple DL transmissions are performed from one or more TRPs. 、 base station and systems One of the aims is to provide [Means for solving the problem]

[0009] A terminal according to one aspect of the present disclosure includes: The radio communication system includes a receiving unit that receives information related to the configuration of a multi-PDSCH (Physical Downlink Shared Channel) or information related to the number of repetitions of the PDSCH, and a control unit that controls the reception of a plurality of PDSCHs scheduled by DCI (Downlink Control Information), and when the multi-PDSCH is configured, the information related to the number of repetitions of the PDSCH is not configured. [Effects of the Invention]

[0010] According to one aspect of the present disclosure, communication can be performed appropriately even when multiple DL transmissions are performed from one or more TRPs. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram illustrating an example of scheduling control of a physical shared channel based on PDCCH / DCI. [Figure 2] 2A-2D illustrate an example of a multi-TRP scenario. [Figure 3] FIG. 3 is a diagram showing cases of combinations of PDCCH types / configurations and multi-PDSCH types / configurations. [Figure 4] FIG. 4 is a diagram showing an example of Case 1 in this embodiment. [Figure 5] 5A and 5B are diagrams showing an example of the fallback operation in Case 1 according to the present embodiment. [Figure 6] FIG. 6 is a diagram showing an example of Case 2 in this embodiment. [Figure 7] FIG. 7 is a diagram showing an example of the fallback operation in Case 2 in this embodiment. [Figure 8] FIG. 8 is a diagram showing an example of Case 3 in this embodiment. [Figure 9] FIG. 9 is a diagram showing an example of the fallback operation in Case 3 in this embodiment. [Figure 10] FIG. 10 is a diagram showing an example of Case 4 in this embodiment. [Figure 11] FIG. 11 is a diagram showing an example of Case 5 in this embodiment. [Figure 12] FIG. 12 is a diagram showing an example of Case 6 in this embodiment. [Figure 13] FIG. 13 is a diagram showing an example of Case 7 / 8 in this embodiment. [Figure 14] 14A and 14B are diagrams showing an example of the case 9-1 / 9-2 in this embodiment. [Figure 15] FIG. 15 is a diagram showing an example of case 10 in this embodiment. [Figure 16]FIG. 16 is a diagram showing an example of Case 11 in this embodiment. [Figure 17] FIG. 17 is a diagram showing an example of Case 12 / 13 in this embodiment. [Figure 18] 18A and 18B are diagrams illustrating an example of mapping of TCI states for multi-PDSCH. [Figure 19] 19A and 19B are diagrams illustrating other examples of mapping of TCI states for multi-PDSCH. [Figure 20] FIG. 20 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 21] FIG. 21 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 22] FIG. 22 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 23] FIG. 23 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. [Figure 24] FIG. 24 is a diagram illustrating an example of a vehicle according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] (Time domain resource allocation) In existing systems (e.g., Rel. 15), time-domain resource allocation information for a physical shared channel (at least one of a PDSCH and a PUSCH) is included in downlink control information (DCI). A network (e.g., a base station) uses a predetermined field (e.g., a TDRA field) included in the DCI to notify a UE of information regarding the time-domain resource in which the physical shared channel scheduled in the DCI is scheduled.

[0013] The information regarding the time domain resource may include, for example, at least one of information indicating the offset between the DCI and the physical shared channel (e.g., slot offset K0), information indicating the start symbol (e.g., start symbol S), and information indicating the length of the physical shared channel (e.g., length L).

[0014] Each bit information (or code point) notified in the TDRA field may be associated with a different time domain resource allocation candidate (or entry). For example, a table (e.g., a TDRA table) in which each bit information is associated with the time domain resource allocation candidates (K0, S, L) may be defined. The time domain resource allocation candidates may be predefined in a specification or may be notified / configured to the UE by higher layer signaling.

[0015] [PDSCH] The UE may determine a row index (entry number or entry index) in a predetermined table based on the value of the TDRA field in the DCI (e.g., DCI format 1_0 / 1_1 / 1_2). The predetermined table may include at least one of information indicating a time offset (e.g., slot offset K0) between the DCI and the PDSCH scheduled by the DCI, information indicating a mapping type of the PDSCH, and a start symbol S and a time length L of the PDSCH. The combination of the start symbol S and the time length L of the PDSCH may be referred to as a Start and Length Indicator (SLIV).

[0016] The UE may determine the time domain resource on which the PDSCH is scheduled based on the value of a predetermined field included in the DCI and at least one of slot offset K0 information, mapping type, start symbol S, symbol length L, and SLIV specified in the table (see FIG. 1). Note that the reference points of the start symbol S and symbol length L may be controlled based on the start position (first symbol) of the slot. Also, the start symbol S, symbol length L, etc. may be defined according to the mapping type of the PDSCH.

[0017] As shown in Figure 1, the UE determines the slot in which the PDSCH is scheduled, using the DCI (or the PDCCH used to transmit the DCI) as a reference point in the time domain. For example, when the UE receives DCI scheduling the PDSCH in slot #n, it determines the slot number n and the subcarrier spacing μ for the PDSCH. PDSCH , subcarrier spacing for PDCCH μ PDCCH The slot for receiving the PDSCH (allocated to the PDSCH) may be determined based on at least one of the time offsets K0. Here, the case is shown where the slot offset K0=1 and the subcarrier intervals of the PDSCH and PDCCH are the same.

[0018] Furthermore, the UE determines the allocation of the PDSCH based on the resource allocation information (e.g., SLIV) specified in the TDRA field, using the starting point of the slot to which the PDSCH is allocated as a reference point. Note that the reference point may also be called a reference point or a reference point.

[0019] [PUSCH] The UE may determine a row index (entry number or entry index) in a predetermined table based on the value of the TDRA field in the DCI (e.g., DCI format 0_0 / 0_1 / 0_2). The predetermined table may include at least one of information indicating a time offset (e.g., slot offset K2) between the DCI and the PUSCH scheduled by the DCI, information indicating a mapping type of the PUSCH, and a start symbol S and a duration L of the PUSCH. The combination of the start symbol S and duration L of the PUSCH may be referred to as a Start and Length Indicator (SLIV).

[0020] The UE may determine the time domain resource on which the PUSCH is scheduled based on the value of a predetermined field included in the DCI and at least one of slot offset K2 information, mapping type, start symbol S, symbol length L, and SLIV specified in the table (see FIG. 1). Note that the reference points of the start symbol S and symbol length L may be controlled based on the start position (first symbol) of the slot. Also, the start symbol S, symbol length L, etc. may be defined according to the mapping type of the PDSCH.

[0021] As shown in Figure 1, the UE determines the slot in which the PUSCH is scheduled, using the DCI (or the PDCCH used to transmit the DCI) as a reference point in the time domain. For example, when the UE receives DCI scheduling the PUSCH in slot #n+4, it determines the slot number n+4 and the subcarrier spacing μ for the PUSCH. PDSCH , subcarrier spacing for PUCCH μ PDCCH The slot for transmitting the PUSCH (allocated to the PUSCH) may be determined based on at least one of the time offsets K2. Here, the case is shown where the slot offset K2=3 and the subcarrier intervals of the PDSCH and PDCCH are the same.

[0022] Furthermore, the UE determines the allocation of the PUSCH based on the resource allocation information (for example, SLIV) specified in the TDRA field, using the start point of the slot to which the PUSCH is allocated as a reference.

[0023] (Multi-TRP) In NR, one or more Transmission / Reception Points (TRPs) (multi-TRP) are considered to perform DL transmission to a UE using one or more panels (multi-panel), and a UE is considered to perform UL transmission to one or more TRPs.

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

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

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

[0027] 2B shows an example of a case where only one TRP (TRP1 in this example) transmits a control signal to a UE, and the TRP transmits a data signal (this case may be called a single master mode). The UE receives each PDSCH transmitted from the TRP based on one Downlink Control Information (DCI).

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

[0029] 2D shows an example of a case where each of the multiple TRPs transmits a separate control signal to the UE, and the multiple TRPs transmit data signals (this may be referred to as a multi-master mode). A first control signal (DCI) may be transmitted from TRP1, and a second control signal (DCI) may be transmitted from TRP2. The UE receives each PDSCH transmitted from the multiple TRPs based on these DCIs.

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

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

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

[0033] Note that multiple PDSCHs (multi-PDSCHs) that are non-coherent may be defined as partially or completely overlapping in at least one of the time and frequency domains, i.e., 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.

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

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

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

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

[0038] For single PDCCH design (mainly for ideal backhaul), TCI extensions are being considered. Each TCI codepoint in the DCI may correspond to a TCI state of 1 or 2. The TCI field size may be the same as that in Rel. 15.

[0039] (SFN PDCCH) For PDCCH / CORESET specified in Rel. 15, one TCI state without CORESETPoolIndex (which may also be called TRP information (TRP Info)) is set to one CORESET.

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

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

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

[0043] Furthermore, in repeated transmission 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 one CORESET, one (maximum one) TCI state can be configured / activated by higher layer signaling (RRC signaling / MAC CE).

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

[0045] When scheduling multiple PDSCHs for multiple TRPs using DCI, it is assumed that the DCI supports a single DCI field (e.g., Transmission Configuration Indication) for TCI notification. The single DCI field (or single DCI field) may reuse the TCI status indication mechanism for multiple TRPs in Rel. 16.

[0046] A single DCI field may indicate one or more (e.g., two) TCI states associated with a codepoint for a single DCI-based multi-TRP mechanism, where a multi-PDSCH using a single DCI in multi-TRP (e.g., S-DCI M-TRP multi-PDSCH) (Scheme 1 or Scheme 2) is considered.

[0047] Alternatively, a single DCI field may indicate only one TCI state associated with a codepoint for a multi-TRP mechanism based on multi-DCI, which is considered as a multi-PDSCH using multi-DCI in multi-TRP (M-DCI multi-PDSCH).

[0048] RRC configuration and activation / deactivation by the MAC CE may apply to one or more TCI states.

[0049] When multi-PDSCH transmission is supported in single-TRP / multi-TRP, the question arises as to how to set / apply / determine the QCL / TCI states associated with the multi-PDSCHs (e.g., the association between each PDSCH and the QCL / TCI state).

[0050] For example, in Rel. 17 and later, in addition to a single PDCCH (no repetition), it is expected that at least one of PDCCH repetition and a PDCCH using a single frequency network (e.g., a single frequency network (SFN)) (e.g., an SFN PDCCH) will be supported. Also, it is expected that at least one of a multi-PDSCH in a single TRP, a multi-PDSCH transmission using a single DCI in a multi-TRP (Scheme 1 / Scheme 2), a PDSCH using an SFN (SFN PDSCH), and a multi-PDSCH using a multi-DCI in a multi-TRP (e.g., an M-DCI M-TRP multi-PDSCH) will be supported.

[0051] In such a case, the problem arises as to how to control the transmission of multi-PDSCHs scheduled by the PDCCH (or DCI).

[0052] The present inventors have focused on the fact that there are multiple possible cases for multi-PDSCH scheduled by PDCCH, and have considered how to control the reception processing of multi-PDSCH in each case (including whether reception is performed / whether support is performed) and have come up with the idea for this embodiment.

[0053] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. Note that each of the following aspects (for example, each case) may be used alone, or at least two of them may be combined and applied.

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

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

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

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

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

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

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

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

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

[0063] In the present disclosure, it is assumed that the multiple PDSCHs (or DL-SCH / CW / TB) / PUSCHs (or UL-SCHs) have different contents, but this is not limitative.

[0064] The DCI in the following embodiments may be limited to a specific DCI format among DCI formats for scheduling a PDSCH (for example, DCI formats 1_0, 1_1, and 1_2), or may correspond to multiple DCI formats. Note that when multiple DCI formats are applicable, common control (the same control and the same processing) may be performed for all DCI formats, or different control may be performed for each DCI format.

[0065] In the following embodiments, "plurality" and "two" may be read interchangeably.

[0066] (Wireless communication method) In the present disclosure, the type / configuration of a PDCCH used to schedule a multi-PDSCH (or a PDCCH providing DCI for scheduling a multi-PDSCH) may be at least one of a single PDCCH, a PDCCH repetition (e.g., PDCCH repetition), and a PDCCH using SFN (e.g., SFN PDCCH).

[0067] The single PDCCH (for example, no repetition) may be a PDCCH to which repeated transmission is not applied, or a PDCCH in which the number of repetitions is one.

[0068] In this disclosure, configuring / indicating PDCCH repetition may mean configuring / indicating that two SS sets / CORESETs / PDCCH candidates are linked for PDCCH repetition. The PDCCH repetition scheme of Rel. 17 may be reused.

[0069] In the present disclosure, configuring / indicating an SFN PDCCH may mean configuring / indicating a CORESET with two TCI states / QCLs (or associating two TCI states / QCLs with a CORESET, or configuring a CORESET with two TCI states / QCLs). The SFN PDCCH scheme of Rel. 17 may be reused.

[0070] In the present disclosure, the type / configuration of the multi-PDSCH may be at least one of a multi-PDSCH in a single TRP (e.g., S-TRP multi-PDSCH), a multi-PDSCH using a single DCI in a multi-TRP (e.g., S-DCI M-TRP multi-PDSCH (scheme 1 / scheme 2)), a multi-PDSCH using SFN (e.g., SFN multi-PDSCH), and a multi-PDSCH using multi-DCI in a multi-TRP (e.g., M-DCI M-TRP multi-PDSCH).

[0071] Configuring / indicating multi-PDSCH may mean that a predetermined field in the DCI supports scheduling of multi-PDSCH. The predetermined field may be a time resource allocation field (e.g., a TDRA field). An index specified in the TDRA field may be associated with a combination of predetermined parameters. The combination of predetermined parameters may be defined as a table (e.g., a TDRA table).

[0072] A row (e.g., row) in the TDRA table may indicate consecutive or non-consecutive slots of the PDSCH / PUSCH based on a predetermined parameter. The predetermined parameter may be a SLIV, a mapping type, or a scheduling offset corresponding to the PDSCH / PUSCH. The PDSCH / PUSCH allocated to consecutive or non-consecutive slots can be indicated based on a combination of a value of the TDRA field (e.g., a row index in the TDRA table) and a predetermined parameter corresponding to the value.

[0073] The multiple PDSCHs (or multiple PDSCHs) may be configured to be time-multiplexed (e.g., TDM). For example, the multiple PDSCHs may be scheduled in different slots. Furthermore, the time-multiplexed multiple PDSCHs may be subject to the same frequency domain resource allocation (e.g., FDRA).

[0074] Configuring / indicating multiple PDSCHs in a single TRP may mean that a single TCI state / QCL is configured / indicated and that the single TCI state / QCL applies to multiple PDSCHs (e.g., all scheduled PDSCHs).

[0075] Configuring / indicating multiple PDSCHs using a single DCI in multiple TRPs (Scheme 1) may mean that two TCI states / QCLs are configured / indicated and applied to multiple PDSCHs, where each PDSCH may be associated with one TCI state / QCL.

[0076] Configuring / indicating multi-PDSCH (Scheme 2) using a single DCI in multi-TRP may mean configuring / indicating two TCI states / QCLs and applying them to multiple PDSCHs. Each PDSCH may be configured / indicated as a multi-TRP TDM / FDM / SDM PDSCH scheme. In this case, the multi-TRP TDM / FDM / SDM PDSCH scheme supported in Rel. 16 may be reused. For example, "each PDSCH" in a multi-PDSCH may include multiple PDSCHs (e.g., the first PDSCH included in the multi-PDSCH may include multiple PDSCHs), and the multiple PDSCHs may be transmitted (e.g., repeatedly transmitted) using TDM / FDM / SDM.

[0077] Configuring / indicating an M-TRP TDM PDSCH may mean that a TDM scheme (e.g., tdmSchemeA) is configured as an upper layer parameter (e.g., repetitionScheme) indicating the repetition scheme, or that an upper layer parameter (e.g., repetitionNumber) indicating the number of repetitions is configured.

[0078] Configuring / indicating an M-TRP FDM PDSCH may mean that a first FDM scheme (e.g., fdmSchemeA) or a second FDM scheme (e.g., fdmSchemeB) is configured as an upper layer parameter (e.g., repetitionScheme) indicating the repetition scheme.

[0079] Configuring / indicating an M-TRP SDM PDSCH may mean that DMRS ports of two CDM groups are indicated.

[0080] In the multi-PDSCH using single DCI in multi-TRP (Scheme 2), different PDSCHs may be associated with different schemes (e.g., S-TRP, M-TRP TDM, M-TRP FDM, or M-TRP SDM). The association may be predefined in the specification or configured / instructed by higher layer signaling / MAC CE, etc.

[0081] In scheme 1 of multi-PDSCH using single DCI in multi-TRP, among multiple PDSCHs scheduled by single DCI, different PDSCHs are transmitted in different beams (or TCI states / QCLs), and each PDSCH may be transmitted in only one beam. That is, each PDSCH may be an S-TRP PDSCH transmission. In scheme 2 of multi-PDSCH using single DCI in multi-TRP, each PDSCH may be transmitted in two beams, that is, each PDSCH may correspond to a repetition of an M-TRP PDSCH.

[0082] Configuring / indicating multi-PDSCH using multi-DCI in multi-TRP may mean that a CORESET pool index (e.g., 0 or 1) is configured in the CORESET that schedules the PDSCH. If a CORESET pool index ID is configured in any CORESET (or at least one CORESET), other CORESETs in which a CORESET pool index ID is not configured may be considered to have a CORESET pool index = 0 (or may be considered to have a CORESET pool ID configured).

[0083] Configuring / indicating a multi-PDSCH using SFN may mean configuring / indicating two TCI states / QCLs and applying the two TCI states / QCLs to the multi-PDSCH. Each PDSCH may be associated with two TCI states / QCLs, and each PDSCH may be configured / indicated as an SFN PDSCH scheme. The SFN PDSCH scheme of Rel. 17 may be reused.

[0084] Below, we will explain combinations of the type / configuration of the PDCCH used for scheduling the multi-PDSCH and the type / configuration of the multi-PDSCH. In the following explanation, we will explain cases 1 to 13 (see FIG. 3) as examples, but the combinations are not limited to these.

[0085] <Case 1> For multi-PDSCH (scheme 1) using single PDCCH + single DCI in multi-TRP (e.g., single PDCCH + S-DCI M-TRP multi-PDSCH (scheme 1)), at least one of the following options 1-1 to 1-2 may be applied / supported.

[0086] Fig. 4 shows an example of Case 1. Fig. 4 shows a case where the same / single PDCCH (or DCI) schedules multiple PDSCHs #1 to #4. The multiple PDSCHs #1 to #4 may correspond to different TBs (or CWs). Furthermore, the multiple PDSCHs (or PDSCHs corresponding to different TBs) may be transmitted using different time intervals (for example, slots). In other words, the multiple PDSCHs may be transmitted using multiple slots.

[0087] [Option 1-1] A configuration may be adopted in which multi-PDSCH (scheme 1) using single PDCCH+single DCI in multi-TRP is not supported. Note that in the following description, support may be interpreted as configuration / activation / validation.

[0088] The UE may not assume / expect that multi-PDSCH (scheme 1) using a single DCI in multi-TRP (e.g., S-DCI M-TRP multi-PDSCH (scheme 1)) will be configured / indicated.

[0089] For example, the UE may not assume that a multi-PDSCH is configured / indicated in the serving cell / BWP and that there is a TCI codepoint (at least one codepoint) that is simultaneously mapped to two TCI states / QCLs.

[0090] Alternatively, the UE may not assume / expect that multi-PDSCH is configured / indicated in the serving cell / BWP. In such a case, there may be a TCI codepoint (at least one codepoint) that is mapped to two TCI states / QCLs in the serving cell / BWP.

[0091] Alternatively, the UE may not assume that the DCI indicates multi-PDSCH and that the DCI indicates TCI codepoints that are mapped to two TCI states / QCLs.

[0092] When a multi-PDSCH is configured / indicated, or when a multi-PDSCH is indicated by DCI and a TCI codepoint that is mapped to two TCI states / QCLs is indicated, the UE may be controlled (e.g., fallback) to perform a predetermined operation.

[0093] The predetermined operation may be, for example, a reception operation for multiple PDSCHs in a single TRP. When falling back to the operation for multiple PDSCHs in a single TRP, for example, the UE may control to apply only the first (or second) TCI state or only the TCI state with a lower (or higher) ID to all PDSCHs.

[0094] 5A shows an example of UE operation when falling back to multi-PDSCH operation in a single TRP. In FIG. 5A, the UE may apply only the first TCI state (or only the second TCI state) to PDSCHs #1 to #4 to control reception of multiple PDSCHs.

[0095] Alternatively, the predetermined operation may be a reception operation for a single PDSCH in a single TRP. When falling back to the operation for a single PDSCH in a single TRP, for example, the UE may be controlled to apply only the first (or second) TCI state or only the TCI state with a lower (or higher) ID to the predetermined PDSCH. The predetermined PDSCH may be the PDSCH transmitted first in the time domain, and in this case, the UE may be controlled to receive only the PDSCH transmitted first.

[0096] 5B illustrates an example of UE operation when falling back to single PDSCH operation in a single TRP. In FIG. 5B, the UE may apply only the first TCI state (or only the second TCI state) and control to receive only a specific PDSCH (e.g., PDSCH#1). If PDSCH#1 corresponds to two TCI states, the UE may determine the TCI state corresponding to PDSCH#1 based on a predetermined rule. The predetermined rule may be defined based on the index of the TCI state (e.g., the lowest TCI state ID).

[0097] In the present disclosure, configuring / indicating multi-PDSCH may mean that no row (or any corresponding index) in the configured TDRA table (or an association set of multiple time-domain parameters) includes more than one SLIV (one set of start symbol and length). Alternatively, it may mean that the configured TDRA table includes at least a row (or index) having more than one SLIV, but the DCI does not indicate that row.

[0098] [Option 1-2] A configuration may be adopted in which multiple PDSCHs (Scheme 1) using a single PDCCH and a single DCI are supported in multiple TRPs. In this case, the UE may assume / expect the contents shown in Option 1-1 (for example, "not assumed / expected" in Option 1-1 may be read as "assumed / expected").

[0099] In this case, one of multiple (e.g., two) TCI states may be applied to each PDSCH, and the mapping (or association) of the two TCI states to the multiple PDSCHs may be controlled based on a predetermined rule.

[0100] 4 shows a case where a first TCI state is applied to PDSCHs #1 and #3 with odd indexes, and a second TCI state is applied to PDSCHs #2 and #4 with even indexes. Note that the TCI states corresponding to each PDSCH are not limited to this.

[0101] <Case 2> For multi-PDSCH (scheme 2) using single PDCCH + single DCI in multi-TRP (e.g., single PDCCH + S-DCI M-TRP multi-PDSCH (scheme 2)), at least one of the following options 2-1 to 2-2 may be applied / supported.

[0102] Fig. 6 shows an example of Case 2. Fig. 6 shows a case where the same / single PDCCH (or DCI) schedules multiple PDSCHs #1 to #4. The multiple PDSCHs #1 to #4 may correspond to different TBs (or CWs). Furthermore, the multiple PDSCHs (or PDSCHs corresponding to different TBs) may be transmitted using different time intervals (for example, slots). In other words, the multiple PDSCHs may be transmitted using multiple slots.

[0103] Furthermore, a scheduled PDSCH (or a PDSCH in a certain slot) may be received from multiple TRPs (M-TRP repetition). In this case, the PDSCH in a certain slot (e.g., PDSCH corresponding to the same TB) may be transmitted from multiple TRPs. Also, different TCI states / QCLs may be applied to the PDSCH transmitted from each TRP. The UE may control reception using one or more TCI states (e.g., a first TCI state and a second TCI state) for one or more PDSCHs transmitted in a certain slot.

[0104] [Option 2-1] A configuration may be adopted in which multi-TRP does not support multi-PDSCH (scheme 2) using single PDCCH+single DCI.

[0105] The UE may not assume / expect that multi-PDSCH (scheme 2) using a single DCI in multi-TRP (e.g., S-DCI M-TRP multi-PDSCH (scheme 2)) will be configured / indicated.

[0106] For example, the UE may not assume that multi-PDSCH is configured / indicated in the serving cell / BWP and that a multi-TRP scheme (e.g., MTRP TDM / FDM / SDM) is configured / indicated at the same time.

[0107] Alternatively, the UE may not assume / expect that multi-PDSCH is configured / indicated in the serving cell / BWP. In such a case, the serving cell / BWP may configure / indicate a multi-TRP scheme (e.g., MTRP TDM / FDM / SDM).

[0108] Alternatively, the UE may not assume that the DCI indicates multiple PDSCHs and that the DCI indicates two TCI states / QCLs.

[0109] When multi-PDSCH is configured / indicated, or when multi-PDSCH is indicated by DCI and two TCI states / QCLs are indicated, the UE may be controlled (e.g., fallback) to perform a predetermined operation.

[0110] The predetermined operation may be, for example, a reception operation for multiple PDSCHs in a single TRP. When falling back to the operation for multiple PDSCHs in a single TRP, for example, the UE may control to apply only the first (or second) TCI state or only the TCI state with a lower (or higher) ID to all PDSCHs.

[0111] For example, the UE may apply only the first TCI state (or only the second TCI state) to PDSCHs #1 to #4, and perform control to receive a plurality of PDSCHs (see FIG. 5A).

[0112] Alternatively, the predetermined operation may be a reception operation for a single PDSCH in a single TRP. When falling back to the operation for a single PDSCH in a single TRP, for example, the UE may be controlled to apply only the first (or second) TCI state or only the TCI state with a lower (or higher) ID to the predetermined PDSCH. The predetermined PDSCH may be the PDSCH transmitted first in the time domain, and in this case, the UE may be controlled to receive only the PDSCH transmitted first.

[0113] For example, the UE may be controlled to apply only the first TCI state (or only the second TCI state) and receive only a specific PDSCH (for example, PDSCH#1) (see FIG. 5B).

[0114] Alternatively, the predetermined operation may be a reception operation for a single PDSCH using a single DCI in multi-TRP (e.g., S-DCI M-TRP single PDSCH). When falling back to the operation of a single PDSCH using a single DCI in multi-TRP, for example, the UE may be controlled to receive only the first PDSCH having two TCI states as a multi-TRP scheme (e.g., MTRP TDM / FDM / SDM).

[0115] 7 shows an example of UE operation when falling back to single PDSCH operation using a single DCI in multi-TRP. In FIG. 7, the UE may be controlled to receive only a specific PDSCH (e.g., PDSCH#1) in consideration of multiple TCI states (e.g., a first TCI state and a second TCI state) as an M-TRP method.

[0116] [Option 2-2] A configuration may be adopted in which multiple PDSCHs (Scheme 2) using a single PDCCH and a single DCI are supported in multiple TRPs. In this case, the UE may assume / expect the contents shown in Option 2-1 (for example, "not assumed / expected" in Option 2-1 may be read as "assumed / expected").

[0117] In this case, multiple (e.g., two) TCI states may be applied to each PDSCH (e.g., PDSCH in each slot). Also, each PDSCH may be configured to be received based on a multi-TRP scheme (e.g., MTRP TDM / FDM / SDM).

[0118] 6 shows a case where a first TCI state and a second TCI are applied to each of PDSCHs #1 to #4. The UE may control reception of each PDSCH by taking into account the first TCI state and the second TCI based on a multi-TRP scheme (e.g., MTRP TDM / FDM / SDM).

[0119] <Case 3> For a multi-PDSCH using a single PDCCH and SFN (for example, single PDCCH + SFN multi-PDSCH), at least one of the following options 3-1 to 3-2 may be applied / supported.

[0120] Fig. 8 shows an example of Case 3. Fig. 8 shows a case where the same / single PDCCH (or DCI) schedules multiple PDSCHs #1 to #4. The multiple PDSCHs #1 to #4 may correspond to different TBs (or CWs). Furthermore, the multiple PDSCHs (or PDSCHs corresponding to different TBs) may be transmitted using different time intervals (for example, slots). In other words, the multiple PDSCHs may be transmitted using multiple slots.

[0121] Each of PDSCHs #1 to #4 may be associated with two TCI states / QCLs, and each of PDSCHs #1 to #4 may be configured / instructed as an SFN PDSCH scheme. The UE may be controlled to receive one or more PDSCHs transmitted in a certain slot using one or more TCI states (e.g., a first TCI state and a second TCI state).

[0122] [Option 3-1] A configuration may be adopted in which multi-PDSCH using SFN is not supported.

[0123] The UE may not assume / expect that a multi-PDSCH using SFN (for example, an SFN multi-PDSCH) will be configured / indicated.

[0124] For example, the UE does not need to assume that a multi-PDSCH is configured / instructed in the serving cell / BWP and that an SFN PDSCH scheme is configured / instructed at the same time.

[0125] Alternatively, the UE may not assume or expect that a multi-PDSCH is configured or indicated in the serving cell / BWP. In such a case, an SFN PDSCH scheme (e.g., an SFN PDSCH scheme) may be configured or indicated in the serving cell / BWP.

[0126] Alternatively, the UE may not assume that the DCI indicates multiple PDSCHs and that the DCI indicates two TCI states / QCLs.

[0127] When multi-PDSCH is configured / indicated, or when multi-PDSCH is indicated by DCI and two TCI states / QCLs are indicated, the UE may be controlled (e.g., fallback) to perform a predetermined operation.

[0128] The predetermined operation may be, for example, a reception operation for multiple PDSCHs in a single TRP. When falling back to the operation for multiple PDSCHs in a single TRP, for example, the UE may control to apply only the first (or second) TCI state or only the TCI state with a lower (or higher) ID to all PDSCHs.

[0129] For example, the UE may apply only the first TCI state (or only the second TCI state) to PDSCHs #1 to #4, and perform control to receive a plurality of PDSCHs (see FIG. 5A).

[0130] Alternatively, the predetermined operation may be a reception operation for a single PDSCH in a single TRP. When falling back to the operation for a single PDSCH in a single TRP, for example, the UE may be controlled to apply only the first (or second) TCI state or only the TCI state with a lower (or higher) ID to the predetermined PDSCH. The predetermined PDSCH may be the PDSCH transmitted first in the time domain, and in this case, the UE may be controlled to receive only the PDSCH transmitted first.

[0131] For example, the UE may be controlled to apply only the first TCI state (or only the second TCI state) and receive only a specific PDSCH (for example, PDSCH#1) (see FIG. 5B).

[0132] Alternatively, the predetermined operation may be a reception operation for a single PDSCH using SFN (for example, SFN single PDSCH). When falling back to the operation of the single PDSCH using SFN, for example, the UE may be controlled to receive only the first PDSCH having two TCI states as the SFN PDSCH scheme.

[0133] 9 shows an example of UE operation when falling back to single PDSCH operation using SFN. In FIG. 9, the UE may be controlled to receive only a specific PDSCH (e.g., PDSCH#1) in consideration of multiple TCI states (e.g., a first TCI state and a second TCI state) as the SFN PDSCH scheme.

[0134] [Option 3-2] A configuration that supports multi-PDSCH using SFN may be used. In this case, the UE may assume / expect the contents shown in Option 3-1 (for example, "not assumed / expected" in Option 3-1 may be read as "assumed / expected").

[0135] In this case, multiple (for example, two) TCI states may be applied to each PDSCH (for example, the PDSCH of each slot), and each PDSCH may be configured to be received based on the SFN PDSCH scheme.

[0136] 8 shows a case where a first TCI state and a second TCI are applied to each of PDSCHs #1 to #4. The UE may control reception of each PDSCH in consideration of the first TCI state and the second TCI based on the SFN PDSCH scheme.

[0137] <Case 4> For a multi-PDSCH using a single PDCCH + multi-DCI in multi-TRP (for example, single PDCCH + M-DCI M-TRP multi-PDSCH), at least one of the following options 4-1 to 4-2 may be applied / supported.

[0138] Fig. 10 shows an example of Case 4. Fig. 10 shows a case where the same / single PDCCH (or DCI) schedules multiple PDSCHs #1 to #4. A predetermined CORESET pool index (for example, CORESET pool ID = 0 or 1) may be set for one PDCCH (or a CORESET corresponding to the PDCCH).

[0139] The multiple PDSCHs #1 to #4 may correspond to different TBs (or CWs). Furthermore, the multiple PDSCHs (or PDSCHs corresponding to different TBs) may be transmitted using different time intervals (for example, slots). In other words, the multiple PDSCHs may be transmitted using multiple slots.

[0140] Furthermore, for a certain scheduled PDSCH (or a PDSCH in a certain slot), the TCI state / QCL associated with the CORESET pool ID corresponding to the PDCCH (or PDCCH) may be applied.

[0141] [Option 4-1] A configuration may be adopted in which multiple PDSCHs using multiple DCIs are not supported in multiple TRPs.

[0142] The UE does not need to assume / expect that a multi-PDSCH using a multi-DCI in a multi-TRP (for example, an M-DCI M-TRP multi-PDSCH) will be configured / indicated.

[0143] For example, the UE does not need to assume that there exists a CORESET in which multi-PDSCH is configured / indicated and a CORESET pool ID is configured / indicated at the same time in the serving cell / BWP.

[0144] Alternatively, the UE may not assume / expect that multi-PDSCH is configured / indicated in the serving cell / BWP. In such a case, there may be any CORESET (at least one CORESET) in which a CORESET pool ID is configured / indicated in the serving cell / BWP.

[0145] Alternatively, for DCI detected in a CORESET for which a CORESET pool ID is configured / indicated, the UE may not assume / do not expect the DCI to indicate multi-PDSCH.

[0146] [Option 4-2] A configuration may be adopted in which multiple PDSCHs using multiple DCIs are supported in multiple TRPs. In this case, the UE may assume / expect the contents shown in Option 4-1 (for example, "not assumed / expected" in Option 4-1 may be read as "assumed / expected").

[0147] In this case, one TCI state / QCL may be indicated by the DCI, and this TCI state / QCL may be applied to all PDSCHs.

[0148] 10 shows a case where a first TCI state (or a second TCI) is applied to each of PDSCHs #1 to #4. The UE may control reception of each PDSCH by using the TCI state / QCL corresponding to the CORESET pool ID corresponding to the PDCCH (or DCI) that schedules the PDSCHs #1 to #4, or the TCI state / QCL indicated by the DCI.

[0149] <Case 5> For multi-PDSCH using PDCCH repetition in a single TRP (for example, PDCCH repetition + S-TRP multi-PDSCH), at least one of the following options 5-1 to 5-2 may be applied / supported.

[0150] Figure 11 shows an example of a multi-PDSCH using PDCCH repetition in a single TRP. Figure 11 shows a case where PDCCH repetition (for example, multiple PDCCHs (or DCIs)) schedules multiple PDSCHs #1 to #4. Search space sets / CORESETs / PDCCH candidates corresponding to multiple PDCCHs may be linked / associated.

[0151] The multiple PDSCHs #1 to #4 may correspond to different TBs (or CWs). Furthermore, the multiple PDSCHs (or PDSCHs corresponding to different TBs) may be transmitted using different time intervals (for example, slots). In other words, the multiple PDSCHs may be transmitted using multiple slots.

[0152] [Option 5-1] A configuration may be adopted in which multi-PDSCH using PDCCH repetition is not supported in a single TRP.

[0153] The UE may not assume / expect that PDCCH repetition indicates multi-PDSCH in a single TRP (e.g., S-TRP multi-PDSCH).

[0154] For example, the UE may not assume that there is a search space set / CORESET (e.g., at least one search space set / CORESET) in the serving cell / BWP in which multi-PDSCH is configured / indicated and at the same time configured / indicated as PDCCH repetition.

[0155] Alternatively, the UE may not assume / expect that a multi-PDSCH is configured / indicated in the serving cell / BWP. In such a case, there may be a search space set / CORESET (e.g., at least one search space set / CORESET) configured / indicated as PDCCH repetition in the serving cell / BWP.

[0156] Alternatively, the UE may not assume that DCI detected in a search space set / CORESET / PDCCH candidate configured / indicated as PDCCH repetition indicates multi-PDSCH.

[0157] If a multi-PDSCH is configured / indicated, or if a multi-PDSCH is indicated by DCI and there is a search space set / CORESET configured / indicated as PDCCH repetition, the UE may be controlled (e.g., fallback) to perform a predetermined operation.

[0158] The predetermined operation may be, for example, a reception operation for a single PDSCH. When falling back to the operation for a single PDSCH, for example, the UE may be controlled to receive only a specific PDSCH (for example, the first PDSCH).

[0159] [Option 5-2] A single TRP may be configured to support multiple PDSCHs using PDCCH repetition. In this case, the UE may assume / expect the contents shown in Option 5-1 (for example, "not assumed / expected" in Option 5-1 may be read as "assumed / expected").

[0160] In this case, one TCI state / QCL may be indicated by the DCI, and this TCI state / QCL may be applied to all PDSCHs.

[0161] Furthermore, a reference PDCCH candidate (for example, a reference PDCCH candidate) among two linked PDCCH candidates for PDCCH repetition may be determined based on a predetermined rule. The reference PDCCH candidate may be used for timeline / beam determination, etc.

[0162] The predetermined rule may be the start timing / end timing / CORESET ID / search space set ID of the PDCCH candidate (or the corresponding CORESET / search space set) in the time domain. For example, among multiple linked PDCCH candidates, the PDCCH candidate that starts earliest, starts latest, ends earliest, or ends latest in the time domain may be the reference PDCCH candidate. Alternatively, the PDCCH candidate with the lowest (or highest) corresponding CORESET ID or the lowest (or highest) corresponding service space set ID may be the reference PDCCH candidate.

[0163] <Case 6> For multi-PDSCH (scheme 1) using PDCCH repetition in multi-TRP + single DCI (e.g., PDCCH repetition + S-DCI M-TRP multi-PDSCH (scheme 1)), at least one of the following options 6-1 to 6-2 may be applied / supported.

[0164] Figure 12 shows an example of Case 6. Figure 12 shows a case where PDCCH repetition (e.g., multiple PDCCHs (or DCIs)) schedules multiple PDSCHs #1 to #4. Search space sets / CORESETs / PDCCH candidates corresponding to the multiple PDCCHs may be linked / associated.

[0165] The multiple PDSCHs #1 to #4 may correspond to different TBs (or CWs). Furthermore, the multiple PDSCHs (or PDSCHs corresponding to different TBs) may be transmitted using different time intervals (for example, slots). In other words, the multiple PDSCHs may be transmitted using multiple slots.

[0166] [Option 6-1] A configuration may be adopted in which multi-PDSCH (scheme 1) using PDCCH repetition + single DCI in multi-TRP is not supported.

[0167] The UE does not need to assume / expect that PDCCH repetition will configure / indicate multi-PDSCH (scheme 1) using a single DCI in multi-TRP (e.g., S-DCI M-TRP multi-PDSCH (scheme 1)).

[0168] For example, the UE may not assume that there is configuration information in the serving cell / BWP that configures / indicates multi-PDSCH and simultaneously configures / indicates PDCCH repetition. The configuration information may be a search space set / CORESET (e.g., at least one search space set / CORESET) / PDCCH candidate.

[0169] Alternatively, the UE may not assume / expect that a multi-PDSCH is configured / indicated in the serving cell / BWP. In such a case, there may be a search space set / CORESET (e.g., at least one search space set / CORESET) that is configured / indicated as PDCCH repetition in the serving cell / BWP.

[0170] Alternatively, the UE may not assume that for DCI detected in a search space set / CORESET / PDCCH candidate configured / indicated as PDCCH repetition, the DCI indicates a multi-PDSCH (Scheme 1) using a single DCI.

[0171] When a multi-PDSCH is configured / indicated, or when a multi-PDSCH is indicated by DCI and there is a search space set / CORESET configured / indicated as PDCCH repetition, the UE may be controlled to perform a predetermined operation (for example, fallback). The predetermined operation (for example, fallback operation) may apply the configuration shown in Option 1-1 of Case 1.

[0172] [Option 6-2] A configuration may be adopted in which multiple PDSCHs (Scheme 1) using PDCCH repetition and single DCI are supported in multiple TRPs. In this case, the UE may assume / expect the contents shown in Option 6-1 (for example, "not assumed / expected" in Option 6-1 may be read as "assumed / expected").

[0173] In this case, one of multiple (e.g., two) TCI states may be applied to each PDSCH, and the mapping (or association) of the two TCI states to the multiple PDSCHs may be controlled based on a predetermined rule.

[0174] 12 shows a case where a first TCI state is applied to PDSCHs #1 and #3 with odd indexes, and a second TCI state is applied to PDSCHs #2 and #4 with even indexes. Note that the TCI states corresponding to each PDSCH are not limited to this.

[0175] Furthermore, a reference PDCCH candidate (e.g., a reference PDCCH candidate) among two linked PDCCH candidates for PDCCH repetition may be determined based on a predetermined rule. The reference PDCCH candidate may be used for timeline / beam determination, etc. The predetermined rule may apply the configuration shown in Option 5-2 of Case 5.

[0176] <Case 7 / 8> For Case 7, which corresponds to multi-PDSCH using PDCCH repetition in multi-TRP + single DCI (scheme 2) (e.g., PDCCH repetition + S-DCI M-TRP multi-PDSCH (scheme 2)), at least one of the following options 7-1 to 7-2 may be applied / supported. Alternatively, for Case 8, which corresponds to multi-PDSCH using PDCCH repetition and SFN (e.g., PDCCH repetition + SFN multi-PDSCH), at least one of the following options 8-1 to 8-2 may be applied / supported.

[0177] Fig. 13 shows an example of Case 7 / Case 8. Fig. 13 shows a case where PDCCH repetition (for example, multiple PDCCHs (or DCIs)) schedules multiple PDSCHs #1 to #4. Search space sets / CORESETs / PDCCH candidates corresponding to the multiple PDCCHs may be linked / associated.

[0178] The multiple PDSCHs #1 to #4 may correspond to different TBs (or CWs). Furthermore, the multiple PDSCHs (or PDSCHs corresponding to different TBs) may be transmitted using different time intervals (for example, slots). In other words, the multiple PDSCHs may be transmitted using multiple slots.

[0179] Furthermore, a scheduled PDSCH (or a PDSCH in a certain slot) may be received from multiple TRPs (M-TRP repetition). In this case, the PDSCH in a certain slot (e.g., PDSCHs corresponding to the same TB) may be transmitted from multiple TRPs. Different TCI states / QCLs may be applied to the PDSCHs transmitted from each TRP. Alternatively, each of PDSCHs #1 to #4 may be associated with two TCI states / QCLs, and each of PDSCHs #1 to #4 may be configured / instructed as an SFN PDSCH scheme. The UE may perform control so that reception is performed using one or more TCI states (e.g., a first TCI state and a second TCI state) for one or more PDSCHs transmitted in a certain slot.

[0180] [Option 7-1 / 8-1] A configuration may be adopted in which multi-PDSCH (Scheme 2) using a single DCI in multi-TRP is not supported due to PDCCH repetition. Also, a configuration may be adopted in which multi-PDSCH using SFN is not supported due to PDCCH repetition. In the following description, a multi-PDSCH (Scheme 2) using a single DCI in multi-TRP is used as an example, but the same may be applied to a multi-PDSCH using SFN.

[0181] The UE does not need to assume / expect that PDCCH repetition will configure / indicate multi-PDSCH (scheme 2) using a single DCI in multi-TRP (e.g., S-DCI M-TRP multi-PDSCH (scheme 2)). Note that multi-PDSCH (scheme 2) using a single DCI in multi-TRP may be interpreted as multi-PDSCH using SFN.

[0182] For example, the UE may not assume that there is configuration information in which multi-PDSCH is configured / indicated and PDCCH repetition is configured / indicated at the same time in the serving cell / BWP. The configuration information may be a search space set / CORESET (e.g., at least one search space set / CORESET) / PDCCH candidate.

[0183] Alternatively, the UE may not assume / expect that a multi-PDSCH is configured / indicated in the serving cell / BWP. In such a case, there may be a search space set / CORESET (e.g., at least one search space set / CORESET) configured / indicated as PDCCH repetition in the serving cell / BWP.

[0184] Alternatively, the UE may not assume that a DCI detected in a search space set / CORESET / PDCCH candidate configured / indicated as PDCCH repetition indicates a multi-PDSCH (Scheme 2) using a single DCI / a multi-PDSCH using SFN.

[0185] When a multi-PDSCH is configured / indicated, or when a multi-PDSCH is indicated by DCI and there is a search space set / CORESET configured / indicated as PDCCH repetition, the UE may be controlled to perform a predetermined operation (for example, fallback). The predetermined operation (for example, fallback operation) may apply the configuration shown in Option 2-1 / 3-1 of Case 2 / 3.

[0186] [Option 7-2 / 8-2] A configuration may be adopted in which multiple PDSCHs (Scheme 2) using a single DCI are supported in multiple TRPs by PDCCH repetition. Also, a configuration may be adopted in which multiple PDSCHs using SFN are supported by PDCCH repetition. In this case, the UE may assume / expect the contents shown in Option 7-1 / 8-1 (for example, "assume / expect" in Option 7-1 / 8-1 may be read as "assume / expect").

[0187] In this case, multiple (e.g., two) TCI states may be applied to each PDSCH (e.g., PDSCH of each slot). Also, each PDSCH may be configured to be received based on a multi-TRP scheme (e.g., MTRP TDM / FDM / SDM) or SFN PDSCH scheme.

[0188] 13 shows a case where a first TCI state and a second TCI are applied to each of PDSCHs #1 to #4. The UE may control reception of each PDSCH by taking into account the first TCI state and the second TCI based on a multi-TRP scheme (e.g., MTRP TDM / FDM / SDM) or an SFN PDSCH scheme.

[0189] Furthermore, a reference PDCCH candidate (e.g., a reference PDCCH candidate) among two linked PDCCH candidates for PDCCH repetition may be determined based on a predetermined rule. The reference PDCCH candidate may be used for timeline / beam determination, etc. The predetermined rule may apply the configuration shown in Option 5-2 of Case 5.

[0190] <Case 9> For multi-PDSCH using PDCCH repetition in multi-TRP + multi-DCI (for example, PDCCH repetition + M-DCI M-TRP multi-PDSCH), at least one of the following options 9-1 to 9-2 may be applied / supported.

[0191] 14A and 14B show an example of Case 9. In FIG. 14A and 14B, a PDCCH repetition (e.g., multiple PDCCHs (or DCIs)) schedules multiple PDSCHs #1 to #4. The search space sets / CORESETs / PDCCH candidates corresponding to the multiple PDCCHs may be linked / associated.

[0192] The multiple PDSCHs #1 to #4 may correspond to different TBs (or CWs). Furthermore, the multiple PDSCHs (or PDSCHs corresponding to different TBs) may be transmitted using different time intervals (for example, slots). In other words, the multiple PDSCHs may be transmitted using multiple slots.

[0193] The CORESET pool indexes corresponding to multiple (e.g., two) search space sets / CORESETs / PDCCH candidates (or multiple linked search space sets / CORESETs / PDCCH candidates) for PDCCH repetition may be set to the same value (Case 9-1, see FIG. 14A). Here, the case where both CORESET pool indices corresponding to two linked PDCCHs (or search space sets / CORESETs / PDCCH candidates) are set to 0 (or 1) is shown.

[0194] The CORESET pool indexes corresponding to multiple (e.g., two) search space sets / CORESETs / PDCCH candidates (or multiple linked search space sets / CORESETs / PDCCH candidates) for PDCCH repetition may be set to different values ​​(Case 9-2, see FIG. 14B). Here, a case is shown in which one of the CORESET pool indices corresponding to two linked PDCCHs (or search space sets / CORESETs / PDCCH candidates) is set to 0 and the other is set to 1.

[0195] Also, in Case 9-1 / 9-2, for a certain scheduled PDSCH (or a PDSCH in a certain slot), a specific (for example, one) TCI state / QCL indicated by the DCI may be applied.

[0196] Case 9-1 [Option 9-1] A configuration may be adopted in which multi-PDSCH indicated by PDCCH repetition with the same CORESET pool index is not supported. Multi-PDSCH corresponds to multi-PDSCH using multi-DCI in multi-TRP (for example, M-DCI M-TRP multi-PDSCH).

[0197] The UE may not assume / expect that a multi-PDSCH is configured / indicated by two linked search space sets / CORESETs (or corresponding PDCCHs / DCIs) for PDCCH repetitions with the same CORESET pool index configured.

[0198] [Option 9-2] A configuration may be adopted in which multiple PDSCHs indicated by PDCCH repetitions with the same CORESET pool index are supported. In this case, the UE may assume / expect the contents indicated in Option 9-1 (for example, "not assumed / expected" in Option 9-1 may be read as "assumed / expected").

[0199] In this case, one TCI state / QCL may be indicated by DCI (for example, DCI provided by a repeated PDCCH), and the TCI state / QCL indicated by the DCI may be applied to all PDSCHs.

[0200] 14A shows a case where either the first TCI state or the second TCI (here, the first TCI state) is applied to each of PDSCHs #1 to #4. The UE may determine the TCI state / QCL to apply to reception processing of PDSCHs #1 to #4 based on information included in DCI provided by PDCCH repetition.

[0201] Case 9-2 [Option 9-1] A configuration may be adopted in which multi-PDSCH indicated by PDCCH repetition with different CORESET pool indices is not supported. Multi-PDSCH corresponds to multi-PDSCH using multi-DCI in multi-TRP (for example, M-DCI M-TRP multi-PDSCH).

[0202] The UE may not assume / expect that a multi-PDSCH is configured / indicated by two linked search space sets / CORESETs (or corresponding PDCCHs / DCIs) for PDCCH repetitions with different CORESET pool indices configured.

[0203] [Option 9-2] A configuration may be adopted in which multiple PDSCHs indicated by PDCCH repetitions with different CORESET pool indices are supported. In this case, the UE may assume / expect the contents indicated in Option 9-1 (for example, "assume / expect" in Option 9-1 may be read as "assume / expect").

[0204] In this case, one TCI state / QCL may be indicated by DCI (for example, DCI provided by a repeated PDCCH), and the TCI state / QCL indicated by the DCI may be applied to all PDSCHs.

[0205] 14B shows a case where either the first TCI state or the second TCI (here, the first TCI state) is applied to each of PDSCHs #1 to #4. The UE may determine the TCI state / QCL to apply to reception processing of PDSCHs #1 to #4 based on information included in DCI provided by PDCCH repetition.

[0206] <Case 10> For a multi-PDSCH using an SFN PDCCH in a single TRP (for example, SFN PDCCH + S-TRP multi-PDSCH), at least one of the following options 10-1 to 10-2 may be applied / supported.

[0207] Fig. 15 shows an example of Case 10. Fig. 15 shows a case where the SFN PDCCH schedules a plurality of PDSCHs #1 to #4.

[0208] The multiple PDSCHs #1 to #4 may correspond to different TBs (or CWs). Furthermore, the multiple PDSCHs (or PDSCHs corresponding to different TBs) may be transmitted using different time intervals (for example, slots). In other words, the multiple PDSCHs may be transmitted using multiple slots.

[0209] Two TCI states / QCLs may be configured / indicated for the CORESET corresponding to the SFN PDCCH.

[0210] [Option 10-1] A configuration may be adopted in which multi-PDSCH using SFN PDCCH is not supported in a single TRP.

[0211] The UE may not assume / expect that the SFN PDCCH indicates multi-PDSCH in a single TRP (eg, S-TRP multi-PDSCH).

[0212] For example, the UE may not assume that a multi-PDSCH is configured / indicated in the serving cell / BWP and that there is simultaneously configuration information configured / indicated as an SFN PDCCH. The configuration information may be a search space set / CORESET (e.g., at least one search space set / CORESET) / PDCCH candidate.

[0213] Alternatively, the UE may not assume / expect that a multi-PDSCH is configured / indicated in the serving cell / BWP, in which case there may be a search space set / CORESET (e.g., at least one search space set / CORESET) configured / indicated as an SFN PDCCH in the serving cell / BWP.

[0214] Alternatively, the UE may not assume that DCI detected in a search space set / CORESET / PDCCH candidate configured / indicated as an SFN PDCCH indicates a multi-PDSCH.

[0215] If a multi-PDSCH is configured / indicated, or if a multi-PDSCH is indicated by DCI and there is a search space set / CORESET configured / indicated as an SFN PDCCH, the UE may be controlled (e.g., fallback) to perform a predetermined operation.

[0216] The predetermined operation may be, for example, a reception operation for a single PDSCH. When falling back to the operation for a single PDSCH, for example, the UE may be controlled to receive only a specific PDSCH (for example, the first PDSCH).

[0217] [Option 10-2] A single TRP may be configured to support multiple PDSCHs using SFN PDCCHs. In this case, the UE may assume / expect the contents shown in Option 10-1 (for example, "not assumed / expected" in Option 10-1 may be read as "assumed / expected").

[0218] In this case, one TCI state / QCL may be indicated by the DCI, and this TCI state / QCL may be applied to all PDSCHs.

[0219] Furthermore, a reference PDCCH candidate (e.g., a reference PDCCH candidate) among two linked PDCCH candidates for the SFN PDCCH may be determined based on a predetermined rule. The reference PDCCH candidate may be used for timeline / beam determination, etc.

[0220] The predetermined rule may be the start timing / end timing / CORESET ID / search space set ID of the PDCCH candidate (or the corresponding CORESET / search space set) in the time domain. For example, among multiple linked PDCCH candidates, the PDCCH candidate that starts earliest, starts latest, ends earliest, or ends latest in the time domain may be the reference PDCCH candidate. Alternatively, the PDCCH candidate with the lowest (or highest) corresponding CORESET ID or the lowest (or highest) corresponding service space set ID may be the reference PDCCH candidate.

[0221] <Case 11> For multi-PDSCH using SFN PDCCH + single DCI in multi-TRP (for example, SFN PDCCH + S-DCI M-TRP multi-PDSCH (scheme 1)), at least one of the following options 11-1 to 11-2 may be applied / supported.

[0222] Fig. 16 shows an example of Case 11. Fig. 16 shows a case where the SFN PDCCH schedules a plurality of PDSCHs #1 to #4.

[0223] The multiple PDSCHs #1 to #4 may correspond to different TBs (or CWs). Furthermore, the multiple PDSCHs (or PDSCHs corresponding to different TBs) may be transmitted using different time intervals (for example, slots). That is, the multiple PDSCHs may be transmitted using multiple slots. Furthermore, some of the multiple PDSCHs #1 to #4 (here, PDSCHs #1 and #3) may correspond to a first TCI state, and the other PDSCHs (here, PDSCHs #2 and #4) may correspond to a second TCI state.

[0224] [Option 11-1] A configuration may be adopted in which multi-TRP does not support multi-PDSCH (scheme 1) using SFN PDCCH+single DCI.

[0225] The UE does not need to assume / expect that the SFN PDCCH will configure / indicate a multi-PDSCH (scheme 1) using a single DCI in multi-TRP (e.g., S-DCI M-TRP multi-PDSCH (scheme 1)).

[0226] For example, the UE may not assume that a multi-PDSCH is configured / indicated in the serving cell / BWP and that there is simultaneously a search space set / CORESET (e.g., at least one search space set / CORESET) configured / indicated as an SFN PDCCH.

[0227] Alternatively, the UE may not assume / expect that a multi-PDSCH is configured / indicated in the serving cell / BWP, in which case there may be a search space set / CORESET (e.g., at least one search space set / CORESET) configured / indicated as an SFN PDCCH in the serving cell / BWP.

[0228] Alternatively, the UE may not assume that DCI detected in a search space set / CORESET / PDCCH candidate configured / indicated as an SFN PDCCH indicates a multi-PDSCH (Scheme 1) using a single DCI.

[0229] When a multi-PDSCH is configured / indicated, or when a multi-PDSCH is indicated by DCI and there is a search space set / CORESET configured / indicated as an SFN PDCCH, the UE may be controlled to perform a predetermined operation (for example, fallback). The predetermined operation (for example, fallback operation) may apply the configuration shown in Option 1-1 of Case 1.

[0230] [Option 11-2] A configuration may be adopted in which multi-TRP supports multi-PDSCH (Scheme 1) using SFN PDCCH + single DCI. In this case, the UE may assume / expect the contents shown in Option 11-1 (for example, "not assumed / expected" in Option 11-1 may be read as "assumed / expected").

[0231] In this case, one of multiple (e.g., two) TCI states may be applied to each PDSCH, and the mapping (or association) of the two TCI states to the multiple PDSCHs may be controlled based on a predetermined rule.

[0232] 16 shows a case where a first TCI state is applied to PDSCHs #1 and #3 with odd indexes, and a second TCI state is applied to PDSCHs #2 and #4 with even indexes. Note that the TCI states corresponding to each PDSCH are not limited to this.

[0233] Furthermore, a reference PDCCH candidate (e.g., a reference PDCCH candidate) of two linked PDCCH candidates for the SFN PDCCH may be determined based on a predetermined rule. The reference PDCCH candidate may be used for timeline / beam determination, etc. The predetermined rule may apply the configuration shown in Option 5-2 of Case 5.

[0234] <Case 12 / 13> For case 12, which corresponds to multi-PDSCH using SNF PDCCH + single DCI in multi-TRP (scheme 2) (e.g., SFN PDCCH + S-DCI M-TRP multi-PDSCH (scheme 2)), at least one of the following options 12-1 to 12-2 may be applied / supported. Alternatively, for case 13, which corresponds to multi-PDSCH using SFN PDCCH and SFN (e.g., SFN PDCCH + SFN multi-PDSCH), at least one of the following options 13-1 to 13-2 may be applied / supported.

[0235] Figure 17 shows an example of Case 12 / Case 13. Figure 17 shows a case where an SFN PDCCH schedules multiple PDSCHs #1 to #4. The search space sets / CORESETs / PDCCH candidates corresponding to the SFN PDCCHs may be linked / associated.

[0236] The multiple PDSCHs #1 to #4 may correspond to different TBs (or CWs). Furthermore, the multiple PDSCHs (or PDSCHs corresponding to different TBs) may be transmitted using different time intervals (for example, slots). In other words, the multiple PDSCHs may be transmitted using multiple slots.

[0237] Furthermore, a scheduled PDSCH (or a PDSCH in a certain slot) may be received from multiple TRPs (M-TRP repetition). In this case, the PDSCH in a certain slot (e.g., PDSCHs corresponding to the same TB) may be transmitted from multiple TRPs. Different TCI states / QCLs may be applied to the PDSCHs transmitted from each TRP. Alternatively, each of PDSCHs #1 to #4 may be associated with two TCI states / QCLs, and each of PDSCHs #1 to #4 may be configured / instructed as an SFN PDSCH scheme. The UE may perform control so that reception is performed using one or more TCI states (e.g., a first TCI state and a second TCI state) for one or more PDSCHs transmitted in a certain slot.

[0238] [Option 12-1 / 13-1] The SFN PDCCH may be configured not to support multi-PDSCH (Scheme 2) using a single DCI in multi-TRP. Also, the SFN PDCCH may be configured not to support multi-PDSCH using SFN. In the following description, multi-PDSCH (Scheme 2) using a single DCI in multi-TRP is used as an example, but the same may be applied to multi-PDSCH using SFN.

[0239] The UE does not need to assume / expect that the SFN PDCCH will configure / instruct a multi-PDSCH (scheme 2) using a single DCI in multi-TRP (e.g., S-DCI M-TRP multi-PDSCH (scheme 2)). Note that the multi-PDSCH (scheme 2) using a single DCI in multi-TRP may be interpreted as a multi-PDSCH using SFN.

[0240] For example, the UE may not assume that a multi-PDSCH is configured / indicated in the serving cell / BWP and that there is simultaneously a search space set / CORESET (e.g., at least one search space set / CORESET) configured / indicated as an SFN PDCCH.

[0241] Alternatively, the UE may not assume / expect that a multi-PDSCH is configured / indicated in the serving cell / BWP, in which case there may be a search space set / CORESET (e.g., at least one search space set / CORESET) configured / indicated as an SFN PDCCH in the serving cell / BWP.

[0242] Alternatively, the UE may not assume that a DCI detected in a search space set / CORESET / PDCCH candidate configured / indicated as an SNF PDCCH indicates a multi-PDSCH (Scheme 2) using a single DCI / multi-PDSCH using SFN.

[0243] When a multi-PDSCH is configured / indicated, or when a multi-PDSCH is indicated by DCI and there is a search space set / CORESET configured / indicated as an SFN PDCCH, the UE may be controlled to perform a predetermined operation (for example, fallback). The predetermined operation (for example, fallback operation) may apply the configuration shown in Option 2-1 / 3-1 of Case 2 / 3.

[0244] [Option 12-2 / 13-2] The SFN PDCCH may be configured to support multi-PDSCH (Scheme 2) using a single DCI in multi-TRP. Also, the SNF PDCCH may be configured to support multi-PDSCH using SFN. In this case, the UE may assume / expect the contents shown in Option 12-1 / 13-1 (for example, "assume / do not expect" in Option 12-1 / 13-1 may be read as "assume / expect").

[0245] In this case, multiple (e.g., two) TCI states may be applied to each PDSCH (e.g., PDSCH of each slot). Also, each PDSCH may be configured to be received based on a multi-TRP scheme (e.g., MTRP TDM / FDM / SDM) or SFN PDSCH scheme.

[0246] 17 shows a case where a first TCI state and a second TCI are applied to each of PDSCHs #1 to #4. The UE may control reception of each PDSCH by taking into account the first TCI state and the second TCI based on a multi-TRP scheme (e.g., MTRP TDM / FDM / SDM) or an SFN PDSCH scheme.

[0247] Furthermore, a reference PDCCH candidate (e.g., a reference PDCCH candidate) of two linked PDCCH candidates for the SFN PDCCH may be determined based on a predetermined rule. The reference PDCCH candidate may be used for timeline / beam determination, etc. The predetermined rule may apply the configuration shown in Option 5-2 of Case 5.

[0248] <TCI state corresponding to multi-PDSCH> When multiple (e.g., two) TCI states are applied to multiple PDSCHs (e.g., Case 1 / Case 6 / Case 11), one of the two TCI states is applied to each PDSCH. In such a case, the mapping (or correspondence / association) between the multiple TCI states and the multiple PDSCHs may be determined based on a predetermined rule. The predetermined rule may be at least one of Options A-1 / A-2 below.

[0249] Option A-1 A pattern of mapping between two TCI states and multiple PDSCHs may be predefined.

[0250] Option A-2 Multiple patterns of mapping between two TCI states and multiple PDSCHs may be defined in advance. One of the multiple patterns may be notified from the base station to the UE using RRC / MAC CE / DCI, etc. For example, when the base station instructs the UE by DCI which pattern to apply, a new field of the DCI may be applied, or an existing field (e.g., one entry in the TDRA table) may be applied.

[0251] The multiple patterns may include at least one of a cyclic mapping pattern (for example, a cyclic mapping pattern), a sequential mapping pattern (for example, a sequential mapping pattern), and a half-half mapping pattern (for example, a half-half mapping pattern).

[0252] In a cyclic mapping pattern, for example, a first TCI state / QCL and a second TCI state / QCL may be applied to a first PDSCH and a second PDSCH, respectively, and the same mapping pattern may be subsequently applied to the remaining PDSCHs (see FIG. 18A), where the first TCI state / QCL is applied to PDSCHs with odd indices and the second TCI state / QCL is applied to PDSCHs with even indices.

[0253] In a sequential mapping pattern, a first TCI state / QCL may be applied to the first and second PDSCHs, a second TCI state / QCL may be applied to the third and fourth PDSCHs, and the same mapping pattern may be subsequently applied to the remaining PDSCHs (see FIG. 18B). Here, the same TCI state / QCL is applied to X consecutive PDSCHs (here, X=2). Note that X is not limited to 2.

[0254] That is, a first TCI state / QCL may be applied to the first X PDSCHs, a second TCI state / QCL may be applied to the second X PDSCHs, and the same mapping pattern may be subsequently applied to the remaining PDSCHs. Figure 19A shows the case where X=3.

[0255] In the half-half mapping pattern, a first TCI state / QCL may be applied to the first half of a plurality of PDSCHs, and a second TCI state / QCL may be applied to the second half of the PDSCHs (see FIG. 19B). FIG. 19B shows a case where a first TCI state / QCL is applied to the first four PDSCHs PDSCHs #1 to #4 of eight PDSCHs, and a second TCI state / QCL is applied to the last four PDSCHs PDSCHs #5 to #8.

[0256] When the total number of multi-PDSCHs is Y, the first half of the PDSCHs may be determined by introducing Y / 2 into the ceiling function or floor function. The second half of the PDSCHs may be determined by introducing Y / 2 into the floor function or ceiling function, or may be determined by Y-(the value obtained by introducing Y / 2 into the ceiling function or floor function).

[0257] (UE capability information) In the above embodiments (for example, cases 1 to 13), the following UE capabilities may be configured. Note that the following UE capabilities may be interpreted as parameters (for example, higher layer parameters) configured in the UE from the network (for example, base station).

[0258] UE capability information regarding whether each of the above cases (for example, at least one of cases 1 to 13) is supported may be defined.

[0259] UE capability information regarding whether or not a fallback operation / fallback resolution is supported in each of the above cases (for example, at least one of cases 1 to 13) may be defined.

[0260] UE capability information may be defined regarding whether the UE supports a first subcarrier spacing (SCS) / second subcarrier spacing. The first subcarrier spacing may be, for example, 480 kHz, and the second subcarrier spacing may be, for example, 960 kHz.

[0261] UE capability information may be defined regarding whether the UE supports operation in a predetermined frequency range (or frequencies above a predetermined frequency). The predetermined frequency range may be, for example, 52.6 GHz to 71 GHz. Alternatively, the predetermined frequency range may be, for example, FR2-2 (or FR2). The predetermined frequency may be, for example, 52.6 GHz.

[0262] In addition, the subcarrier spacing (e.g., first subcarrier spacing / second subcarrier spacing) is not defined as a UE capability, and whether or not the above embodiment is applicable may be determined depending on whether or not the UE is operating at that subcarrier spacing.

[0263] Alternatively, the predetermined frequency range may not be defined as a UE capability, and whether or not the above embodiment is applicable may be determined depending on whether or not the UE operates in the predetermined frequency range.

[0264] The above embodiments may be applied to a UE that supports / reports at least one of the above UE capabilities, or may be applied to a UE that is configured by the network.

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

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

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

[0268] 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.

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

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

[0271] 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).

[0272] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band 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 be a frequency band higher than FR2.

[0273] Furthermore, the user terminal 20 may perform communication using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.

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

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

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

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

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

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

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

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

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

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

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

[0285] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be called a search space set. Note that the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," "CORESET setting," etc. in the present disclosure may be read interchangeably.

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

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

[0288] 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, 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 as DL-RS.

[0289] 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 the SS (PSS, SSS) and the PBCH (and DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as reference signals.

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

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

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

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

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

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

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

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

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

[0299] The transceiver 120 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

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

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

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

[0303] 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 .

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

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

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

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

[0308] The transmitting / receiving unit 120 may transmit a downlink control channel. The control unit 110 may control a transmission configuration indicator (TCI state) indicated by the downlink control information based on whether or not schedules for multiple downlink shared channels are set or supported at multiple transmitting / receiving points using the downlink control information provided by the downlink control channel.

[0309] The transceiver 120 may transmit a downlink control channel to which repeated transmission or single frequency network transmission is applied. The controller 110 may control the setting information of the downlink control channel based on whether or not schedules for multiple downlink shared channels are set or supported at multiple transmission and reception points using the downlink control information provided by the downlink control channel.

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

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

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

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

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

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

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

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

[0318] The transceiver 220 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

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

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

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

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

[0323] 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.

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

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

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

[0327] The transceiver 220 may receive the downlink control channel. The controller 210 may determine at least one of a transmission configuration indicator (TCI state) indicated by the downlink control information and a TCI state corresponding to the downlink shared channel scheduled by the downlink control information, based on whether or not scheduling of a plurality of downlink shared channels at a plurality of transmission and reception points is set or supported using the downlink control information provided by the downlink control channel.

[0328] When scheduling of multiple downlink shared channels at multiple transmission / reception points is not set or supported and multiple downlink shared channels are scheduled by downlink control information, the control unit 210 may control to receive at least one of the multiple downlink shared channels by using a specific TCI state among the multiple TCI states indicated by the downlink control information.When scheduling of multiple downlink shared channels at multiple transmission / reception points is not set or supported and multiple downlink shared channels are scheduled by downlink control information, the control unit 210 may control to receive a specific downlink shared channel among the multiple downlink shared channels by using the multiple TCI states indicated by the downlink control information.

[0329] When a control resource set pool index is set in a control resource set corresponding to a downlink control channel, the control unit 210 may perform control so that one TCI state included in the downlink control information is applied to the multiple downlink shared channels scheduled in the downlink control information.

[0330] The transceiver 220 may receive a downlink control channel to which repeated transmission or single frequency network transmission is applied. The controller 210 may determine configuration information for the downlink control channel based on whether schedules for multiple downlink shared channels are configured or supported at multiple transmission and reception points using downlink control information provided by the downlink control channel.

[0331] The control unit 210 may control the reception process based on a specific downlink control channel among the downlink control channels to which repeated transmission is applied. Multiple downlink control channels to which repeated transmission is applied may correspond to the same control resource pool index. Multiple downlink control channels to which repeated transmission is applied may correspond to different control resource pool indexes.

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

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

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

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

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

[0337] 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 a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

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

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

[0340] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, a cache, a main memory, or the like. The memory 1002 may store executable programs (program codes), software modules, and the like for implementing a wireless communication method according to an embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0360] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

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

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

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

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

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

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

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

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

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

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

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

[0372] Note that the physical layer signaling may be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be called an RRC message, such as an RRC connection setup message or an RRC connection reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0394] The communication module 60 may transmit at least one of the signals from the various sensors 50-58 input to the electronic control unit 49 and information obtained based on the signals to an external device via wireless communication.

[0395] The communication module 60 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 59 provided in the vehicle. The communication module 60 also stores the various information received from the external devices in a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, various sensors 50-58, and the like provided in the vehicle 40.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A receiving unit that receives information regarding the configuration of a multi-PDSCH (Physical Downlink Shared Channel) or information regarding the number of repetitions of a PDSCH; a control unit that controls reception of a plurality of PDSCHs scheduled by DCI (Downlink Control Information), A terminal in which information regarding the number of repetitions of the PDSCH is not set when the multi-PDSCH is set.

2. A step of receiving information regarding a configuration of a multi-PDSCH (Physical Downlink Shared Channel) or information regarding the number of repetitions of a PDSCH; and controlling reception of a plurality of PDSCHs scheduled by Downlink Control Information (DCI), When the multi-PDSCH is configured, information regarding the number of repetitions of the PDSCH is not configured.

3. A transmitter that transmits information regarding the configuration of a multi-PDSCH (Physical Downlink Shared Channel) or information regarding the number of repetitions of a PDSCH; a control unit that controls transmission of a plurality of PDSCHs scheduled by DCI (Downlink Control Information), A base station that does not set information regarding the number of repetitions of the PDSCH when setting the multi-PDSCH.

4. A system including a terminal and a base station, The terminal a receiving unit that receives information regarding a configuration of a multi-PDSCH (Physical Downlink Shared Channel) or information regarding the number of repetitions of a PDSCH; a control unit that controls reception of a plurality of PDSCHs scheduled by DCI (Downlink Control Information), When the multi-PDSCH is configured, information regarding the number of repetitions of the PDSCH is not configured, The base station A system comprising: a transmitter that transmits information related to the configuration of the multi-PDSCH or information related to the number of repetitions of the PDSCH.

Images