Terminal, wireless communication method, base station and system

Abstract

The present invention appropriately performs communication even when a plurality of DL transmissions / UL transmissions are scheduled by one or more TRPs. A terminal according to an aspect of the present disclosure comprises: a reception unit for receiving downlink control information for scheduling a plurality of shared channels by which an integrated transmission configuration index (TCI) is supported; and a control unit for controlling reception or transmission of the plurality of shared channels, on the basis of a first TCI state commonly set with respect to a plurality of channels or a plurality of transmission directions, or a second TCI state different from the first TCI state.

Description

Terminal, wireless communication method and base station

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

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

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

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

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

[0006] For example, 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 possible to control the schedule of multi-PDSCH transmission / multi-PUSCH transmission 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 NR specifications to date, there has been insufficient consideration given to how to control transmission (e.g., TCI state / QCL assumptions, etc.) when scheduling multiple DL transmissions / UL transmissions from one or more TRPs.

[0008] Therefore, one of the objectives of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can perform communication appropriately even when multiple DL transmissions / UL transmissions are scheduled by one or more TRPs.

[0009] A terminal according to one aspect of the present disclosure includes a receiving unit that receives downlink control information that schedules multiple shared channels for which a unified transmission configuration indicator (TCI) is supported, and a control unit that controls reception or transmission of the multiple shared channels based on a first TCI state that is set commonly for multiple channels or multiple transmission directions, or a second TCI state that is different from the first TCI state.

[0010] According to one aspect of the present disclosure, communication can be performed appropriately even when multiple DL transmissions / UL transmissions are scheduled by one or more TRPs.

[0011] 1A and 1B are diagrams illustrating an example of a unified / common TCI framework. FIG. 2 is a diagram illustrating an example of scheduling control of a physical shared channel based on PDCCH / DCI. FIG. 3 is a diagram illustrating an example of a scheduling offset between a PDCCH and a PDSCH. FIG. 4 is a diagram illustrating another example of a scheduling offset between a PDCCH and a PDSCH. FIG. 5 is a diagram illustrating an example of a case where a multi-PDSCH is scheduled by a PDCCH. FIGS. 6A and 6B are diagrams illustrating an example of an SRI applied to a multi-PUSCH in this embodiment. FIGS. 7A and 7B are diagrams illustrating an example of a TCI state applied to a multi-PDSCH in this embodiment. FIGS. 8A and 8B are diagrams illustrating an example of a TCI state applied to a multi-PUSCH in this embodiment. FIG. 9 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 10 is a diagram illustrating an example of a configuration of a base station according to an embodiment. FIG. 11 is a diagram illustrating an example of a configuration of a user terminal according to an embodiment. FIG. 12 is a diagram illustrating an example of hardware configurations of a base station and a user terminal according to an embodiment. FIG. 13 is a diagram illustrating an example of a vehicle according to an embodiment.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0039] It is being considered that N=M=1 will be supported in Rel. 17. It is being considered that other cases will be supported in Rel. 18 and later.

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

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

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

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

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

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

[0046] The beam instruction DCI for the unified / common TCI state may be DCI format 1_1 / 1_2 with DL assignment (scheduling).

[0047] The beam instruction DCI for the unified / common TCI state may be DCI format 1_1 / 1_2 without DL assignment (scheduling) or a new DCI format, which is useful when there is no DL data but there is beam instruction for the unified / common TCI state.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0061] (QCL Rules) The unified TCI state in Rel. 17 (indicated / updated by Rel. 17 MAC CE / DCI) may or may not be shared with UE-dedicated reception on PDSCH / PDCCH.

[0062] The QCL rules for the Rel. 17 unified TCI state may differ depending on whether the Rel. 17 unified TCI state is shared with UE-specific reception on the PDSCH / PDCCH. For example, for DL ​​channels / RSs that do not share the same Rel. 17 unified TCI state as UE-specific reception on the PDSCH / PDCCH, all QCL rules specified in existing specifications (Options B1 to B3 described below) may be supported. For example, for DL ​​channels / RSs that share the same Rel. 17 unified TCI state as UE-specific reception on the PDSCH / PDCCH, at least one of the QCL rules in Options A1 and A2 below may be supported for the source RS and QCL type. [Option A1] A tracking RS (TRS) is configured for the QCL type A source RS, and a CSI-RS for beam management (BM) (CSI-RS with repetition) is configured for the QCL type D source RS. [Option A2] A TRS is configured for the QCL type A source RS and the QCL type D source RS.

[0063] QCL rules are defined in existing specifications. For example, the following options B1 to B3 are allowed for PDSCH / PDCCH. [Option B1] QCL Type A RS is a TRS (CSI-RS with TRS information (trs-Info)), and Type D RS is a CSI-RS with repetition (CSI-RS for BM). [Option B2] QCL Type A RS is a TRS (CSI-RS with trs-Info), and Type D RS is the same as QCL Type A RS. [Option B3] QCL Type A RS is a CSI-RS without trs-Info and without repetition, and Type D RS is the same as QCL Type A RS.

[0064] For CSI-RS resources in a non-zero power (NZP)-CSI-RS resource set (NZP-CSI-RS-ResourceSet) configured with trs-Info and without repetition, the UE assumes that the TCI-State indicates one of one or more of the following QCL types: Type A with CSI-RS resources in the NZP-CSI-RS resource set configured with trs-Info and, if applicable, Type D with the same CSI-RS resources; Type A with CSI-RS resources in the NZP-CSI-RS resource set configured with trs-Info and, if applicable, Type D with SS / PBCH blocks. Type A with CSI-RS resources in the NZP-CSI-RS resource set configured with trs-Info and, if applicable, Type D with CSI-RS resources in the NZP-CSI-RS resource set configured with repetition, and Type B with CSI-RS resources in the NZP-CSI-RS resource set configured with trs-Info if Type D is not applicable.

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

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

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

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

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

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

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

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

[0073] <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 PDSCH and PUSCH) is included in downlink control information (DCI). A network (e.g., a base station) notifies a UE of information on the time domain resource in which the physical shared channel scheduled by the DCI is scheduled, using a predetermined field (e.g., a TDRA field) included in the DCI.

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

[0075] 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 a time domain resource allocation candidate (K0, S, L) may be defined. The time domain resource allocation candidate may be predefined in a specification or may be notified / configured to a UE by higher layer signaling.

[0076] [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 duration L of the PDSCH. The combination of the start symbol S and duration L of the PDSCH may be referred to as a Start and Length Indicator (SLIV).

[0077] 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. 2 ). 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. Furthermore, the start symbol S, symbol length L, etc. may be defined according to the mapping type of the PDSCH.

[0078] As shown in Figure 2, the UE determines the slot in which the PDSCH is scheduled by 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. ＰＤＳＣＨ , subcarrier spacing for 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 in which the slot offset K0=1, and the subcarrier intervals of the PDSCH and the PDCCH are the same.

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

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

[0081] 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. 2 ). 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. Furthermore, the start symbol S, symbol length L, etc. may be defined according to the mapping type of the PDSCH.

[0082] As shown in Figure 2, 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. ＰＤＳＣＨ , PUCCH subcarrier spacing μ ＰＤＣＣＨ , 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 the PDCCH are the same.

[0083] Furthermore, the UE determines the allocation of the PUSCH based on the starting point of the slot to which the PUSCH is allocated, for resource allocation information (e.g., SLIV) specified in the TDRA field.

[0084] In future NRs, it is possible that either one of the TCI states will be set / applied in order to reduce the load of switching between the unified TCI state introduced / supported in Rel. 17 and the TCI state (e.g., DL) / spatial relationship (e.g., UL) specified in Rel. 15 / 16.

[0085] Although it is assumed that beams (e.g., QCL Type D RSs in TCI states) will be common (e.g., SSBs common between CCs) for each CC in the same band, cases may be considered in which the TCI state / spatial relationship for Rel. 15 and the TCI state for Rel. 17 are configured on different CCs. In this case, it may be possible to clarify the TCI state / spatial relationship for Rel. 15 / 16 and the TCI state for Rel. 17, or to configure only either the TCI state / spatial relationship for Rel. 15 / 16 or the TCI state for Rel. 17 in the same band.

[0086] Furthermore, in consideration of UE load, it is also assumed that a configuration in which only either the TCI state / spatial relationship of Rel. 15 / 16 or the TCI state of Rel. 17 is applied / set in all bands is adopted / set.

[0087] In existing systems (e.g., Rel. 16), for a single PDSCH in a single TRP, if the offset between the DCI and the PDSCH is smaller than a predetermined threshold (e.g., timeDurationForQCL) (see FIG. 3), the UE may assume that the PDSCH (or the DMRS port of the PDSCH) is QCL-aligned with the CORESET with the lowest CORESET ID in the latest slot in the active BWP of the serving cell. That is, the UE may apply the QCL (or TCI state) of the CORESET with the lowest CORESET ID in the latest slot in the active BWP of the serving cell to the PDSCH.

[0088] Also, in existing systems (e.g., Rel. 16), for a single PDSCH in a single TRP, if the offset between the DCI and the PDSCH is equal to or greater than a predetermined threshold (e.g., timeDurationForQCL) and the DCI does not have a TCI field (see FIG. 4), the UE may assume that the QCL of the PDSCH (or the DMRS port of the PDSCH) is the same as the QCL of the CORESET that schedules the PDSCH. The CORESET that schedules the PDSCH may be interpreted as a CORESET that corresponds to the PDCCH / DCI that schedules the PDSCH.

[0089] Incidentally, in Rel. 17 and later, it is assumed that multi-PDSCH scheduled by a single DCI will be supported in a predetermined frequency range (e.g., B52.6 (FR2-2)) (see FIG. 5 ). In this case, how to set the QCL / TCI state (e.g., default QCL / TCI state) of the multi-PDSCH becomes an issue.

[0090] For example, when a multi-PDSCH is configured based on the TCI state / spatial relationship specified in Rel. 15 / 16, at least one of the following cases 1 to 3 may be applied.

[0091] <Case 1> A case is assumed in which the TCI status field is not present in the DCI, the DCI schedules one or more PDSCHs, and the interval between the DCI and the PDSCH (e.g., the PDSCH scheduled first in the time domain) is equal to or greater than a predetermined period (e.g., timeDurationForQCL). In such a case, the QCL assumption / TCI status corresponding to the scheduling PDCCH may be applied to multiple PDSCHs (e.g., all PDSCHs).

[0092] <Case 2> A case is assumed in which the TCI status field is present in the DCI, the DCI schedules one or more PDSCHs, and the interval between the DCI and the PDSCH (e.g., the PDSCH scheduled first in the time domain) is equal to or greater than a predetermined period (e.g., timeDurationForQCL). In such a case, the TCI status indicated by the DCI may be applied to multiple PDSCHs (e.g., all PDSCHs).

[0093] <Case 3> Regardless of whether a TCI status field is present in the DCI, a case may be considered in which the interval between the DCI and a PDSCH (e.g., a PDSCH that is scheduled first in the time domain) is less than a predetermined period (e.g., timeDurationForQCL). In such a case, a predetermined default TCI status may be applied to multiple PDSCHs (e.g., all PDSCHs).

[0094] On the other hand, it is also assumed that a unified TCI state will be configured / applied / activated / supported for a multi-PDSCH / PUSCH in Rel. 17 and later. In other words, when a unified TCI state is configured / activated for a certain transmission direction / one or more channels / signals, how to control the TCI state to be applied / assumed for multiple PDSCHs / PUSCHs (e.g., multi-PDSCHs / PUSCHs) scheduled by DCI becomes an issue.

[0095] The inventors focused on cases where a unified TCI state is set for multiple shared channels, and considered how to set / apply / determine the QCL assumption / TCI state in such cases, and came up with one aspect of this embodiment.

[0096] Furthermore, the inventors of the present invention came up with the idea of ​​one aspect of this embodiment by studying the assumed QCL / TCI state to be applied to each of a plurality of PUSCHs.

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

[0098] 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."

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

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

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

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

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

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

[0105] In the present 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.

[0106] In the present disclosure, the terms common beam, common TCI, common TCI state, Rel. 17 TCI state, Rel. 17 or later TCI state, unified TCI, unified TCI state, TCI state applicable to multiple types of channels / RS, TCI state applied to multiple (multiple types) of channels / RS, TCI state applicable to multiple types of channels / RS, TCI state for multiple types of signals, TCI state for multiple types of channels / RS, TCI state, unified TCI state, UL and DL TCI state for joint TCI indication, UL-only TCI state for separate TCI indication, DL-only TCI state for separate TCI indication, joint TCI state for DL ​​and UL, and separate TCI state for each of DL and UL may be interpreted as interchangeable.

[0107] In the present disclosure, the terms TCI states of Rel. 15 / 16, TCI states / spatial relationships that apply only to specific channels / RSs, and TCI states / spatial relationships that apply to one type of channel / RS may be interpreted interchangeably.

[0108] In the present disclosure, the terms multiple TCI states configured by an RRC IE, multiple TCI states activated by a MAC CE, information regarding one or more TCI states, TCI state configuration, TCI state pool, active TCI state pool, common TCI state pool, unified TCI state pool, TCI state list, unified TCI state list, joint TCI state pool, separate TCI state pool, separate DL / UL TCI state pool, DL TCI state pool, UL TCI state pool, separate DL TCI state pool, and separate UL TCI state pool may be read as interchangeable.

[0109] In the present disclosure, DL TCI, DL only TCI, separate DL only TCI, DL common TCI, DL unified TCI, common TCI, and unified TCI may be interchangeable. In the present disclosure, UL TCI, UL only TCI, separate UL only TCI, UL common TCI, UL unified TCI, common TCI, and unified TCI may be interchangeable.

[0110] In the present disclosure, the channels / RS to which the unified TCI state applies may be PDSCH / PDCCH / CSI-RS / PUSCH / PUCCH / SRS.

[0111] In the present disclosure, BWP, CC (cell), and CC (cell) / BWP may be read interchangeably.

[0112] (Wireless Communication Method) In each embodiment, the Rel. 17 TCI state / unified TCI state may be simply referred to as the TCI state. In each embodiment, when it is necessary to distinguish the Rel. 17 TCI state / unified TCI state from the Rel. 15 / 16 TCI state, it may be referred to as the Rel. 17 TCI state / unified TCI state.

[0113] In each embodiment, the target channel may be at least one of UE-specific reception on PDSCH / PDCCH and PUSCH and dedicated PUCCH resources of a dynamic grant / configuration grant, or at least one of UE-specific reception on PDSCH / PDCCH and PUSCH and all dedicated PUCCH resources of a dynamic grant / configuration grant, or a UE-specific channel / UE-specific reception / UE-specific transmission / UE-specific RS / UE-specific channel resource, or a channel / RS to which a unified TCI state applies.

[0114] In the present disclosure, UE-specific reception on PDSCH / PDCCH, reception of PDSCH / PDCCH configured by PDSCH configuration (PDSCH-Config) / PDCCH configuration (PDCCH-Config), UE-specific PDSCH / PDCCH, and UE-specific PDSCH / PDCCH resources may be interchangeable. In the present disclosure, PUSCH of dynamic grant / configuration grant, PUSCH configured by PUSCH configuration (PUSCH-Config) / configuration grant configuration (ConfiguredGrantConfig), UE-specific PUSCH, and UE-specific PUSCH resource may be interchangeable. In the present disclosure, individual PUCCH resource, PUCCH resource configured by PUCCH configuration (PUCCH-Config), UE-specific PUCCH, and UE-specific PUCCH resource may be interchangeable.

[0115] In each embodiment, a specific channel / signal, a specific channel / signal / resource / resource set, a specific signal, a specific channel, a specific resource, a resource / resource set of a specific channel / RS, a specific channel / RS / resource / resource set, and one of PDSCH / PDCCH / CSI-RS / PUSCH / PUCCH / SRS / CORESET may be read as interchangeable.

[0116] In each embodiment, the following may be interpreted interchangeably: a specific channel / RS sharing the same TCI state as the target channel; a specific channel / RS sharing a TCI state indicated for the target channel; the TCI state of a specific channel / RS being set / indicated together with the TCI state of the target channel; the TCI state of a specific channel / RS referring to the TCI state of the target channel; a TCI state being shared between a specific channel / RS and the target channel; the same TCI state being applied between a specific channel / RS and the target channel; the TCI state of a specific channel / RS being the same as the TCI state of the target channel; the TCI state of a specific channel / RS being the same as the unified TCI state; and the TCI state of a specific channel / RS being updated / indicated / set by the unified TCI state.

[0117] In each embodiment, the TCI state for a particular channel / RS may be the TCI state for only the particular channel / RS or may be the unified TCI state.

[0118] At least one of the following RRC configurations 1 and 2 may be performed for a second channel / signal that can share the same Rel. 17 TCI state as the first channel / RS (Rel. 17 TCI state indicated / updated by the TCI state indication using the Rel. 17 MAC CE / DCI, unified TCI state). The first channel / RS may include UE-dedicated reception on the PDSCH / PDCCH (UE-dedicated PDSCH / PDCCH), PUSCH based on a dynamic grant / configuration grant, or TCI state (unified TCI state / common beam) for all dedicated PUCCH resources (UE-dedicated PUCCH). The indicated Rel. 17 TCI state may be applied to the first / second channel / signal.

[0119] [RRC Configuration 1] For the DL, a second channel / RS for the DL that can share the same Rel. 17 TCI state as the first channel / RS (the Rel. 17 TCI state indicated by the TCI state indication using the Rel. 17 MAC CE / DCI, the unified TCI state) is configured via RRC (RRC IE). The first channel / RS may be in the same TCI state (unified TCI state / common beam) as the TCI state for UE-specific reception of the PDSCH / PDCCH. The second channel for the DL may be a non-UE-dedicated (non-UE dedicated / common / group-common) PDCCH / PDSCH associated with the physical cell identifier (PCI) of the serving cell, or an aperiodic (AP)-CSI-RS for beam management (BM) or CSI.

[0120] [RRC Configuration 2] For the UL, a second channel / RS in the UL that can share the same Rel. 17 TCI state as the first channel / RS (the Rel. 17 TCI state indicated by the TCI state indication using the Rel. 17 MAC CE / DCI, the unified TCI state) is configured via RRC (RRC IE). The first channel / RS may be at least one of a PUSCH based on a dynamic grant / configuration grant and all dedicated PUCCH resources. The second channel in the UL may be an SRS for BM, antenna switching, or codebook / non-codebook-based UL transmission.

[0121] A channel / RS other than the first / second channel / RS may be referred to as a third channel / RS. The third channel / RS may be a channel / RS that cannot share the same Rel. 17 TCI state as the first channel / RS, or a channel / RS other than the first channel / RS that is not configured to be able to share the same Rel. 17 TCI state as the first channel / RS.

[0122] Rel. 17 considers two TCI states: a shared TCI state (a unified TCI state applied to the first and second channels / RSs) shared with a first channel / RS, and a non-shared TCI state (a TCI state for a third channel / RS) that is not shared with the first channel / RS. The shared TCI state may be a unified TCI state / common beam. The non-shared TCI state may be a TCI state for a third channel / RS, a TCI state in Rel. 15 / 16 (a TCI state applied to one type of channel / RS), or a TCI state that is applied to a third channel / RS and is not shared with the first / second channel / RS. When the unified TCI state is updated by one MAC CE / DCI, the shared TCI state (the TCI state applied to the first / second channel / RS) is updated, and the non-shared TCI state (the TCI state applied to the third channel / RS) may not be updated.

[0123] If a UE is configured with Rel. 17 TCI states on any CC, the UE may not assume that it will be configured with Rel. 15 / 16 TCI state / spatial relationship information. This may apply to UEs that support configuring more than N unified TCI states per CC, where N may be 64 for FR2 or the maximum number of SSBs configured for FR1. This prevents simultaneous configuration of Rel. 17 TCI states and Rel. 15 / 16 TCI state / spatial relationship information, thereby reducing UE load.

[0124] In this case, a non-shared TCI state may be set / indicated for a channel / RS in which a unified TCI state / common beam is not set (a third channel / RS, for example, a channel / RS in which a TCI state linked to a common beam should not be updated, such as a TRS or P / SP-CSI-RS). On the other hand, a shared TCI state may be set / indicated for a first channel / RS (for example, a UE-dedicated PDSCH, a PDCCH using a UE-specific search space (USS) (UE-dedicated PDCCH)).

[0125] First Embodiment In the first embodiment, an SRI (SRS indicator) applied to multi-PUSCH will be described.

[0126] The multi-PUSCH may be interpreted as one or more PUSCHs scheduled by one DCI. Furthermore, the multi-PUSCH may be provided for transmitting different data (e.g., transport blocks / UL-SCHs) or may be applied to transmitting the same data.

[0127] When multi-PUSCH is configured / scheduled, at least one of the following options 1-1 to 1-3 may be applied. Note that options 1-1 / 1-2 correspond to the case where the SRI field included in the DCI is not extended, and option 1-3 corresponds to the case where the SRI field is extended.

[0128] [Option 1-1] One SRI (e.g., a spatial domain filter) determined in an existing system (e.g., Rel. 15 / 16) may be applied to multiple scheduled PUSCHs (e.g., all PUSCHs).

[0129] 6A illustrates a case where four PUSCHs (PUSCHs #1 to #4 in this case) are scheduled by DCI (or PDCCH). Also illustrated is a case where a specific SRI (SRI #1 in this case) is indicated by an SRI field (e.g., a certain code point) included in the DCI. The UE may control transmission by applying SRI #1 to each of PUSCHs #1 to #4 based on the DCI.

[0130] [Option 1-2] A higher layer may configure a code point in one SRI field to correspond to multiple SRIs (e.g., spatial domain filters), and the multiple SRIs may be applied to multiple PUSCHs, respectively.

[0131] 6B illustrates a case where four PUSCHs (here, PUSCHs #1 to #4) are scheduled by DCI (or PDCCH). Also, a case where multiple SRIs (here, SRIs #1 to #4) are indicated by an SRI field (e.g., a certain code point) included in the DCI is illustrated. The UE may control transmission by applying SRIs #1 to #4 to each of PUSCHs #1 to #4 based on the DCI.

[0132] [Option 1-3] Two or more SRI fields may be set in the DCI, and each SRI field may indicate an SRI corresponding to each of multiple PUSCHs.

[0133] 6B illustrates a case where four PUSCHs (here, PUSCHs #1 to #4) are scheduled by DCI (or PDCCH). Also, a case where multiple SRIs (here, SRIs #1 to #4) are indicated by multiple SRI fields (e.g., SRI fields #1 to #4) included in the DCI is illustrated. The UE may control transmission by applying SRIs #1 to #4 to each of PUSCHs #1 to #4 based on the multiple SRI fields of the DCI.

[0134] In addition, Option 1-1 to Option 1-3 may be switched and applied based on instructions from the base station (for example, higher layer signaling).

[0135] In this way, by using at least one of Option 1-1 to Option 1-3 to control the spatial relationship (e.g., SRI) applied to the multi-PUSCH, it is possible to perform the multi-PUSCH appropriately.

[0136] Second Embodiment In a second embodiment, a case will be described in which a unified TCI state (for example, Rel. 17 unified TCI state) is set for multi-PDSCH.

[0137] In the present disclosure, whether a unified TCI state (e.g., Rel. 17 TCI state) is applied or a TCI state of an existing system (e.g., Rel. 15 / 16) is applied may be configured / indicated by RRC / MAC CE / DCI.

[0138] The multi-PDSCH (or the TCI state (e.g., unified TCI state) configured for the multi-PDSCH) may be configured to be shared with the target channel (or the same TCI state as the target channel may be indicated) (Case 2-1). The target channel may be UE-dedicated reception on the PDSCH / PDCCH and PUSCH and dedicated PUCCH resources of a dynamic grant / configuration grant.

[0139] Alternatively, the multi-PDSCH (or the TCI state (e.g., unified TCI state) set for the multi-PDSCH) may be configured not to be shared with the target channel (or the same TCI state as that of the target channel may not be indicated) (Case 2-2). In this case, the TCI state of the multi-PDSCH may be determined based on the mechanism of the existing system (e.g., Rel. 15 / 16).

[0140] The unified TCI state may be indicated by MAC CE or MAC CE+DCI. When indicated by DCI, the unified TCI state may be switched after a predetermined period (e.g., Y symbols) has elapsed since the unified TCI state was indicated and an ACK (or ACK / NACK) was transmitted. The predetermined period (e.g., Y) may be reported by UE capability or configured by higher layer parameters.

[0141] Updating / changing the unified TCI state by DCI may be applied to at least case 2-1. Note that in case 2-2, updating / changing the unified TCI state by DCI may not be performed. This is because the TCI state in case 2-2 (for example, the TCI state applied to the multi-PDSCH) may be applied to a UE common RS such as P / SP-CSI, and in such a case, it is difficult to change the beam for each UE.

[0142] When a unified TCI state is applied / configured for multi-PDSCH, the scheduling DCI may be configured not to indicate the beam (e.g., TCI state) of the scheduled PDSCH.

[0143] Therefore, among the above-mentioned cases 1 to 3, the provisions for cases 1 and 3 may be unnecessary.

[0144] For example, if the DCI does not have a TCI status field, the DCI schedules one or more PDSCHs, and the time between the DCI and the PDSCHs is greater than or equal to a predetermined time (e.g., timeDurationForQCL), the unified TCI status may be used to control reception of multiple PDSCHs. Also, regardless of whether the DCI has a TCI status field or not, if the time between the DCI and the PDSCHs is less than a predetermined time, the unified TCI status may be used to apply to multiple PDSCHs (e.g., all PDSCHs).

[0145] Furthermore, when a unified TCI state is configured for multi-PDSCH, a DCI schedules one or more PDSCHs, and the time interval between the DCI and the PDSCHs is equal to or greater than a predetermined time (e.g., timeDurationForQCL), the indicated unified TCI state (e.g., indicated TCI-State) may be applied to multiple PDSCHs (e.g., all PDSCHs). The unified TCI state may be indicated by a predetermined MAC CE / higher layer parameter / DCI.

[0146] When the unified TCI state is updated / changed by the DCI, the UE may apply the update / change of the TCI state a predetermined symbol after the transmission of the ACK (or ACK / NACK). In this case, when multiple PDSCHs are scheduled before and after the predetermined symbol, the updated / changed unified TCI state may be applied to the PDSCHs after the predetermined symbol, and the TCI state before the update / change may be applied to the PDSCHs before the predetermined symbol.

[0147] When the TCI status (e.g., unified TCI status) is indicated using DCI, at least one of Option 2-1 to Option 2-3 below may be applied. Note that Option 2-1 / 2-2 corresponds to the case where the TCI status field included in DCI is not extended, and Option 2-3 corresponds to the case where the TCI status field is extended. When a predetermined upper layer parameter (e.g., a parameter related to the unified TCI status) is set, the TCI status field included in DCI may be interpreted as an indication of the unified TCI status.

[0148] [Option 2-1] One DL / UL TCI or DL-only TCI state may be applied to multiple scheduled PDSCHs (eg, all PDSCHs).

[0149] 7A illustrates a case where four PDSCHs (here, PDSCHs #1 to #4) are scheduled by DCI (or PDCCH). Also, a case where a specific TCI state (here, TCI state #1) is indicated by a TCI state field / beam indication field (e.g., a certain code point) included in the DCI is illustrated. The UE may control reception by applying TCI state #1 to each of PDSCHs #1 to #4 based on the DCI.

[0150] [Option 2-2] A higher layer may configure a codepoint in one TCI status field to correspond to multiple TCI states (e.g., DL / UL TCI state or DL-only TCI state), and the multiple TCI states may be applied to multiple PDSCHs, respectively.

[0151] 7B shows a case where four PDSCHs (here, PDSCHs #1 to #4) are scheduled by DCI (or PDCCH). It also shows a case where multiple TCI states (here, TCI states #1 to #4) are indicated by a TCI state field / beam indication field (e.g., a certain code point) included in the DCI. The UE may control reception by applying TCI states #1 to #4 to each of PDSCHs #1 to #4 based on the DCI.

[0152] [Option 2-3] Two or more TCI status fields may be set in the DCI, and each TCI status field may indicate a TCI status (for example, DL / UL TCI status or DL-only TCI status) corresponding to each of multiple PUSCHs.

[0153] 7B illustrates a case where four PDSCHs (here, PDSCHs #1 to #4) are scheduled by DCI (or PDCCH). Also, a case where multiple TCI states (here, TCI states #1 to #4) are indicated by multiple TCI status fields (e.g., TCI status fields #1 to #4) included in the DCI is illustrated. The UE may control reception by applying TCI states #1 to #4 to each of PDSCHs #1 to #4 based on the multiple TCI status fields of the DCI.

[0154] In Option 2-1 to Option 2-3, if instructed by DCI, the update / change of the TCI state may be applied a predetermined number of symbols after ACK (or ACK / NACK) transmission. Furthermore, the update / change of the TCI state may be instructed by MAC CE instead of DCI. Furthermore, Option 2-1 to Option 2-3 may be switched and applied by an instruction from the base station (for example, higher layer signaling).

[0155] Note that Option 2-1 to Option 2-3 may be applied to a predetermined DCI. The predetermined DCI may be a beam indication DCI without DL assignment (e.g., a beam indication DCI without DL assignment), or may be, for example, a UL grant / group common DCI.

[0156] Third Embodiment In a third embodiment, a case will be described in which a unified TCI state (for example, Rel. 17 unified TCI state) is set for multi-PUSCH.

[0157] The multi-PUSCH (or the TCI state (e.g., the unified TCI state) configured for the multi-PUSCH) may be configured to be shared with the target channel (or the same TCI state as the target channel may be indicated) (Case 3-1). The target channel may be UE-dedicated reception on the PDSCH / PDCCH, and PUSCH and dedicated PUCCH resources of a dynamic grant / configuration grant.

[0158] Alternatively, the multi-PUSCH (or the TCI state (for example, the unified TCI state) set for the multi-PUSCH) may be configured not to be shared with the target channel (or the same TCI state as that of the target channel may not be indicated) (Case 3-2). In this case, the TCI state of the multi-PUSCH may be determined based on the mechanism of the first embodiment.

[0159] The unified TCI state may be indicated by MAC CE or MAC CE+DCI. When indicated by DCI, the unified TCI state may be switched after a predetermined period (e.g., Y symbols) has elapsed since the unified TCI state was indicated and an ACK (or ACK / NACK) was transmitted. The predetermined period (e.g., Y) may be reported by UE capability or configured by higher layer parameters.

[0160] The update / change of the unified TCI state by DCI may be applied to at least case 3-1. Note that in case 3-2, the update / change of the unified TCI state by DCI may not be performed. This is because the TCI state in case 3-2 (for example, the TCI state applied to the multi-PUSCH) may be applied to UE common RS such as P / SP-CSI, and in such a case, it is difficult to change the beam for each UE.

[0161] When a unified TCI state is applied / configured for multi-PUSCH, the scheduling DCI may be configured not to indicate the beam (e.g., TCI state) of the PUSCH scheduled.

[0162] Therefore, among the above-mentioned cases 1 to 3, the provisions for cases 1 and 3 may be unnecessary.

[0163] For example, if the DCI does not have a TCI status field (or an SRI field), the DCI schedules one or more PUSCHs, and the time between the DCI and the PUSCHs is equal to or greater than a predetermined time (e.g., timeDurationForQCL), the unified TCI status may be used to control the transmission of multiple PUSCHs. Furthermore, regardless of whether the DCI has a TCI status field (or an SRI field), if the time between the DCI and the PUSCHs is less than a predetermined time, the unified TCI status may be used to apply to multiple PUSCHs (e.g., all PUSCHs).

[0164] Furthermore, when a unified TCI state is configured for multi-PUSCH, a DCI schedules one or more PUSCHs, and the time interval between the DCI and the PUSCHs is equal to or longer than a predetermined time (e.g., timeDurationForQCL), the indicated unified TCI state (e.g., indicated TCI-State) may be applied to multiple PUSCHs (e.g., all PUSCHs). The unified TCI state may be indicated by a predetermined MAC CE / higher layer parameter / DCI.

[0165] When the unified TCI state is updated / changed by the DCI, the UE may apply the update / change of the TCI state a predetermined symbol after the transmission of the ACK (or ACK / NACK). In this case, when multiple PUSCHs are scheduled before and after the predetermined symbol, the updated / changed unified TCI state may be applied to the PUSCHs after the predetermined symbol, and the TCI state before the update / change may be applied to the PUSCHs before the predetermined symbol.

[0166] When the TCI status (e.g., unified TCI status) is indicated using DCI, at least one of Option 3-1 to Option 3-3 below may be applied. Note that Option 3-1 / 3-2 corresponds to the case where the TCI status field included in DCI is not extended, and Option 2-3 corresponds to the case where the TCI status field is extended. When a predetermined upper layer parameter (e.g., a parameter related to the unified TCI status) is set, the TCI status field included in DCI may be interpreted as an indication of the unified TCI status.

[0167] [Option 3-1] One DL / UL TCI or UL-only TCI state may be applied to multiple scheduled PUSCHs (eg, all PUSCHs).

[0168] 8A illustrates a case where four PUSCHs (here, PUSCHs #1 to #4) are scheduled by DCI (or PDCCH). Also, a case where a specific TCI state (here, TCI state #1) is indicated by a TCI state field / beam indication field (e.g., a certain code point) included in the DCI is illustrated. The UE may control transmission by applying TCI state #1 to each of PUSCHs #1 to #4 based on the DCI.

[0169] [Option 3-2] A higher layer may configure a codepoint in one TCI status field to correspond to multiple TCI states (e.g., DL / UL TCI state or UL-only TCI state), and the multiple TCI states may be applied to multiple PUSCHs, respectively.

[0170] 8B shows a case where four PUSCHs (here, PUSCHs #1 to #4) are scheduled by DCI (or PDCCH). Also, a case where multiple TCI states (here, TCI states #1 to #4) are indicated by a TCI state field / beam indication field (e.g., a certain code point) included in the DCI is shown. The UE may control transmission by applying TCI states #1 to #4 to each of PUSCHs #1 to #4 based on the DCI.

[0171] [Option 3-3] Two or more TCI status fields may be set in the DCI, and each TCI status field may indicate the TCI status (for example, DL / UL TCI status or UL-only TCI status) corresponding to each of multiple PUSCHs.

[0172] 8B illustrates a case where four PUSCHs (here, PUSCHs #1 to #4) are scheduled by DCI (or PDCCH). Also, a case where multiple TCI states (here, TCI states #1 to #4) are indicated by multiple TCI status fields (e.g., TCI status fields #1 to #4) included in the DCI is illustrated. The UE may control transmission by applying TCI states #1 to #4 to each of PUSCHs #1 to #4 based on the multiple TCI status fields of the DCI.

[0173] In Option 3-1 to Option 3-3, if instructed by DCI, the update / change of the TCI state may be applied a predetermined number of symbols after ACK (or ACK / NACK) transmission. Furthermore, the update / change of the TCI state may be instructed by MAC CE instead of DCI. Furthermore, Option 3-1 to Option 3-3 may be switched and applied by an instruction from the base station (for example, higher layer signaling).

[0174] Note that Option 3-1 to Option 3-3 may be applied to a predetermined DCI. The predetermined DCI may be a beam indication DCI without DL assignment (e.g., a beam indication DCI without DL assignment), or may be, for example, a UL grant / group common DCI.

[0175] In the third embodiment, the TCI state is described, but the present invention is not limited to this. For example, when the PL-RS and TPC parameters (P0, α, CL index) are set to be associated with a TCI state, the PL-RS / TPC command parameters may be applied to each PUSCH transmission in conjunction with the TCI state indication.

[0176] <Fourth embodiment> The fourth embodiment describes a case where UE operation is switched depending on the search space type (e.g., common search space (CSS) / UE-specific search space (USS)) / format of DCI, or TCI state / spatial relationship information set for multi-PUSCH / multi-PDSCH.

[0177] The DCI may be a DCI that schedules multi-PUSCH / multi-PDSCH, or a DCI that provides beam indication (or indication of a unified TCI state).

[0178] When the search space type (SS type) of the DCI is USS, at least one of Case 2-1 of the second embodiment and Case 3-1 of the third embodiment may be applied. On the other hand, when the search space type (SS type) of the DCI is CSS, at least one of Case 2-2 of the second embodiment and Case 3-2 of the third embodiment may be applied.

[0179] Furthermore, when the search space type (SS type) of the DCI is USS, at least one of Option 2-2 / 2-3 of the second embodiment and Option 3-2 / 3-3 of the third embodiment may be applied. On the other hand, when the search space type (SS type) of the DCI is USS, at least one of Option 2-1 of the second embodiment and Option 3-1 of the third embodiment may be applied.

[0180] In addition, UE operation may be switched based on the format of the DCI (e.g., whether or not the DCI is in a particular format).

[0181] For example, in the case of DCI format 1_1 / 1_2 / 0_1 / 0_2, at least one of Case 2-1 of the second embodiment and Case 3-1 of the third embodiment may be applied. On the other hand, in the case of any other format (for example, DCI format 1_0 / 0_0 / 2_x), at least one of Case 2-2 of the second embodiment and Case 3-2 of the third embodiment may be applied.

[0182] Furthermore, in the case of DCI format 1_1 / 1_2 / 0_1 / 0_2, at least one of options 2-2 / 2-3 of the second embodiment and options 3-2 / 3-3 of the third embodiment may be applied. On the other hand, in the case of other formats (for example, DCI format 1_0 / 0_0 / 2_x), at least one of option 2-1 of the second embodiment and option 3-1 of the third embodiment may be applied.

[0183] UE operation may be switched based on TCI state / spatial relation information (for example, TCI state / spatial-relation-info) configured for multi-PUSCH / multi-PDSCH.

[0184] For example, when a unified TCI state (e.g., Rel. 17 unified TCI state) is configured for multi-PUSCH / multi-PDSCH, at least one of Case 2-1 of the second embodiment and Case 3-1 of the third embodiment may be applied. On the other hand, when otherwise (e.g., when Rel. 15 / 16 TCI state / spatial relationship information is configured), at least one of Case 2-2 of the second embodiment and Case 3-2 of the third embodiment may be applied.

[0185] Furthermore, when a unified TCI state (e.g., Rel. 17 unified TCI state) is configured for multi-PUSCH / multi-PDSCH, at least one of Option 2-2 / 2-3 of the second embodiment and Option 3-2 / 3-3 of the third embodiment may be applied. On the other hand, when otherwise (e.g., when TCI state / spatial relationship information of Rel. 15 / 16 is configured), at least one of Option 2-1 of the second embodiment and Option 3-1 of the third embodiment may be applied.

[0186] Fifth Embodiment In the fifth embodiment, a case will be described in which a TCI state instruction is performed based on the number of TCI states to be set.

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

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

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

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

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

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

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

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

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

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

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

[0198] Assume that M > 1 / N > 1. In this case, when multiple sets of TCI states (e.g., DL / UL TCI state, DL-only TCI state, UL-only TCI state) are indicated in MAC CE or MAC CE+DCI, the multiple sets of TCI states may be applied to each PDSCH / each PUSCH of multi-PDSCH / multi-PUSCH.

[0199] When M>1 / N>1, the TCI status may be indicated by extending the TCI status field (e.g., by setting multiple TCI status fields in the DCI) and using each TCI status field to indicate multiple TCI statuses.

[0200] When M>1 / N>1, the TCI status may be indicated without extending the TCI status field (e.g., by setting one TCI status field in the DCI). For example, one TCI status field may be used to indicate multiple TCI statuses. For example, RRC / MAC CE may be used to indicate multiple TCI statuses corresponding to one code point in the TCI status field.

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

[0202] (UE Capability Information) In the above-described first to fifth embodiments, the following UE capabilities may be set. Note that the following UE capabilities may be interpreted as parameters (e.g., upper layer parameters) set in the UE from a network (e.g., a base station).

[0203] UE capability information regarding whether each of the above cases / options is supported may be defined. For example, UE capability information regarding whether the PDCCH supports PDCCH repetition may be defined. UE capability information regarding whether the setting / application of a unified TCI state for multi-PDSCH / multi-PUSCH is supported may also be defined.

[0204] UE capability information regarding whether to support a unified TCI state for each CORESET pool index of a multi-PDSCH using multiple DCIs in a multi-TRP may be defined. For example, UE capability information regarding whether to support PDCCH repetition using a unified TCI state may be defined.

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

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

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

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

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

[0210] (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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0236] (Base Station) Fig. 10 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0253] The transceiver 120 may transmit downlink control information that schedules multiple shared channels where a unified transmission configuration indicator (TCI) is supported.

[0254] The control unit 110 may control the reception or transmission of multiple shared channels based on a first TCI state set commonly for multiple channels or multiple transmission directions, or a second TCI state different from the first TCI state.

[0255] (User Terminal) Fig. 11 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0272] The transceiver 220 may receive downlink control information that schedules multiple shared channels that support a unified transmission configuration indicator (TCI). The transceiver 220 may receive information regarding multiple unified TCI states that apply to the multiple shared channels, respectively, using at least one of the downlink control information and the MAC control information.

[0273] The control unit 210 may control the reception or transmission of multiple shared channels based on a first TCI state set commonly for multiple channels or multiple transmission directions, or a second TCI state different from the first TCI state.

[0274] The second TCI state may be indicated by a TCI state notification field included in the downlink control information.

[0275] The control unit 210 may perform control so that the first TCI state is applied to a plurality of TCI states when the interval between the downlink control information and the plurality of shared channels is at least one of a predetermined period or more and a predetermined period or less.

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

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

[0278] For example, a base station, a user terminal, or the like 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. 12 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, and the like.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0308] 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."

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0330] 13 is a diagram illustrating an example of a vehicle according to an embodiment. As shown in FIG. 13, 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0345] 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."

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

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

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

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

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

[0351] 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."

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

[0353] 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."

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

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

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

[0357] This application is based on Japanese Patent Application No. 2021-185997, filed on November 15, 2021, the contents of which are incorporated herein in their entirety.

Claims

1. a receiver for receiving downlink control information (DCI) scheduling a plurality of downlink shared channels (PDSCHs) in which a unified transmission configuration indicator (TCI) is supported; a control unit that controls reception of a PDSCH based on a first TCI state that is set in common for a plurality of channels or a second TCI state that is different from the first TCI state; The control unit controls the terminal so that, among the plurality of PDSCHs, the first TCI state is applied to a PDSCH whose distance from the DCI is less than a predetermined period, and the second TCI state is applied to a PDSCH whose distance from the DCI is more than the predetermined period.

2. The terminal described in claim 1, wherein the control unit determines the TCI state to be applied to the PDSCH depending on the search space type of the DCI.

3. A terminal as described in claim 1 or claim 2, wherein the control unit controls the TCI state set in a higher layer to be applied to the PDSCH when the search space type of the DCI is USS (UE-specific search space).

4. receiving downlink control information (DCI) scheduling a plurality of downlink shared channels (PDSCHs) in which a unified transmission configuration indicator (TCI) is supported; and controlling reception of the PDSCH based on a first TCI state set in common for a plurality of channels or a second TCI state different from the first TCI state, A wireless communication method for a terminal, which controls so that, among the plurality of PDSCHs, the first TCI state is applied to a PDSCH whose distance from the DCI is less than a predetermined period, and the second TCI state is applied to a PDSCH whose distance from the DCI is more than the predetermined period.

5. a transmitter for transmitting downlink control information (DCI) scheduling multiple downlink shared channels (PDSCHs) in which a unified transmission configuration indicator (TCI) is supported; a control unit that controls transmission of a PDSCH based on a first TCI state that is set in common for a plurality of channels or a second TCI state that is different from the first TCI state; The control unit sets, for a terminal, the first TCI state of a PDSCH whose distance from the DCI is less than a predetermined period, and the second TCI state of a PDSCH whose distance from the DCI is more than the predetermined period.

6. A system including a terminal and a base station, The terminal a receiver for receiving downlink control information (DCI) scheduling a plurality of downlink shared channels (PDSCHs) in which a unified transmission configuration indicator (TCI) is supported; a control unit that controls reception of a PDSCH based on a first TCI state that is set in common for a plurality of channels or a second TCI state that is different from the first TCI state; The control unit applies the first TCI state to a PDSCH among the plurality of PDSCHs whose interval with the DCI is less than a predetermined period, and controls to apply the second TCI state to a PDSCH whose interval with the DCI is the predetermined period or more, The base station A system comprising a transmitter that transmits the DCI.