Terminal, wireless communication method, base station and system

Abstract

A terminal according to one aspect of the present disclosure has: a reception unit that receives a configuration indicating whether to follow a specific transmission configuration indication (TCI) state in which scheduling of a physical downlink shared channel (PDSCH) is applied to a plurality of types of signals either of the downlink and the uplink or of the downlink; and a control unit that, on the basis of said configuration, determines a quasi co-location (QCL) assumption for a demodulation reference signal (DMRS) port of the PDSCH. This aspect of the present disclosure makes it possible to appropriately determine the QCL assumption.

Description

Terminal, wireless communication method and base station

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

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

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

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

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

[0006] In addition, it is being considered to indicate TCI states applicable to multiple types of signals (channels / reference signals) by downlink control information. However, the relationship between the timing of the indication and the QCL assumption / TCI state applied to the signal is unclear. If such a relationship is unclear, it may lead to a deterioration in communication quality, a decrease in throughput, etc.

[0007] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that appropriately determine a QCL estimate.

[0008] A terminal according to one aspect of the present disclosure includes a receiving unit that receives a setting indicating whether scheduling of a physical downlink shared channel (PDSCH) follows a specific transmission configuration indication (TCI) state that applies to multiple types of signals, including downlink and uplink, and a control unit that determines a quasi co-location (QCL) assumption for a demodulation reference signal (DMRS) port of the PDSCH based on the setting.

[0009] According to one aspect of the present disclosure, QCL assumptions can be appropriately determined.

[0010] Figures 1A and 1B show an example of a unified / common TCI framework. Figures 2A and 2B show an example of a DCI-based TCI status indication. Figure 3 shows an example of an application time of a unified TCI status indication. Figure 4 shows an example of a default QCL assumption for PDSCH. Figures 5A and 5B show an example of operation of embodiment #2-2-2. Figure 6 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. Figure 7 is a diagram showing an example of a configuration of a base station according to an embodiment. Figure 8 is a diagram showing an example of a configuration of a user terminal according to an embodiment. Figure 9 is a diagram showing an example of a hardware configuration of a base station and a user terminal according to an embodiment. Figure 10 is a diagram showing an example of a vehicle according to an embodiment.

[0011] (Search Space Set) In NR, one or more search space (SS) sets are configured in the UE. The SS set is a set of PDCCH candidates (PDCCH candidates) that the UE monitors. The SS set is also called a PDCCH search space set, search space, etc.

[0012] The UE monitors PDCCH candidates in one or more SS sets, which may include at least one of an SS set common to one or more UEs (common search space (CSS) set) and a SS set specific to a UE (UE-specific search space (USS) set).

[0013] The CSS set may include, for example, at least one of the following: Type 0 - PDCCH CSS set Type 0A - PDCCH CSS set Type 1 - PDCCH CSS set Type 2 - PDCCH CSS set Type 3 - PDCCH CSS set

[0014] A Type-0-PDCCH CSS set may represent a set of CSSs used to monitor DCI formats that are Cyclic Redundancy Check (CRC)-scrambled with the System Information-Radio Network Temporary Identifier (SI-RNTI) in a given cell (e.g., a primary cell). In this disclosure, a Type-0-PDCCH CSS set may also be referred to as a Type-0 CSS / CSS set.

[0015] The Type 0-PDCCH CSS set may be configured in the UE based on information in a Master Information Block (MIB) transmitted on a Physical Broadcast Channel (PBCH) (e.g., the Radio Resource Control (RRC) parameter "pdcch-ConfigSIB1").

[0016] Alternatively, the Type 0-PDCCH CSS set may be configured based on information (e.g., the RRC parameters "searchSpaceSIB1" or "searchSpaceZero") in information about a cell-specific PDCCH (cell-specific PDCCH information, e.g., the RRC parameter "PDCCH-ConfigCommon").

[0017] The cell-specific PDCCH information may be signaled to the UE via system information (e.g., System Information Block (SIB) 1) or UE-specific RRC signaling (e.g., configuration information for synchronization in an RRC reconfiguration message (e.g., the RRC parameter "ReconfigurationWithSync")).

[0018] The Type 0A-PDCCH CSS set may represent a set of CSSs used to monitor DCI formats that are CRC-scrambled with SI-RNTI in a given cell (e.g., a primary cell). The Type 0A-PDCCH CSS set may be configured based on information in cell-specific PDCCH information (e.g., the RRC parameter "searchSpaceOtherSystemInformation"). In this disclosure, the Type 0A-PDCCH CSS set may also be referred to as a Type 0A CSS / CSS set.

[0019] The Type 1-PDCCH CSS set may represent a set of CSSs used to monitor DCI formats that are CRC-scrambled with the Random Access (RA)-RNTI or TC-RNTI in a given cell (e.g., a primary cell). The Type 1-PDCCH CSS set may be configured based on information in cell-specific PDCCH information (e.g., the RRC parameter "ra-SearchSpace"). In this disclosure, the Type 1-PDCCH CSS set may also be referred to as a Type 1 CSS / CSS set.

[0020] The Type 2-PDCCH CSS set may represent a set of CSSs used to monitor DCI formats that are CRC-scrambled with Paging (P)-RNTI in a given cell (e.g., a primary cell). The Type 2-PDCCH CSS set may be configured based on information in cell-specific PDCCH information (e.g., the RRC parameter "pagingSearchSpace"). In this disclosure, the Type 2-PDCCH CSS set may also be referred to as a Type 2 CSS / CSS set.

[0021] The Type 3-PDCCH CSS set may represent a set of CSSs used to monitor at least one of DCI formats CRC-scrambled with Slot Format Indicator (SFI)-RNTI, INT-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, and TPC-SRS-RNTI. The Type 3-PDCCH CSS set may be configured based on information (e.g., the RRC parameter "SearchSpace") in UE-specific PDCCH information (e.g., the RRC parameter "PDCCH-Config"). The UE-specific PDCCH information may be notified to the UE by UE-specific RRC signaling (e.g., an RRC reconfiguration message). In the present disclosure, the Type 3-PDCCH CSS set may also be referred to as a Type 3 CSS / CSS set.

[0022] The USS set may represent a set of USSs used to monitor DCI formats that are CRC-scrambled by the C-RNTI or CS-RNTI. The USS set may be configured based on information in the UE-specific PDCCH information (e.g., the RRC parameter "SearchSpace").

[0023] Each SS set is associated with a control resource set (CORESET). The CORESET may include multiple types (e.g., CORESET #0, a CORESET common to one or more UEs (cell-specific) (common CORESET), and a UE-specific CORESET (individual CORESET)).

[0024] CORESET#0 may be configured based on information (e.g., the RRC parameter "ControlResourceSetzero") in the MIB or the cell-specific PDCCH information (e.g., the RRC parameter "PDCCH-ConfigCommon"). CORESET#0 may be associated with either a CSS set or a USS set.

[0025] The common CORESET may be configured based on information (e.g., the RRC parameter "commonControlResourceSet") in the cell-specific PDCCH information (e.g., the RRC parameter "PDCCH-ConfigCommon"). The common CORESET may be associated with either a CSS set or a USS set.

[0026] A UE-specific CORESET may be configured based on information (e.g., the RRC parameter "ControlResourceSet") in the UE-specific PDCCH information (e.g., the RRC parameter "PDCCH-Config"). The CORESET may be associated with either a CSS set or a USS set. The maximum number of such CORESETs that can be configured per bandwidth part (BWP) in a cell may be specified.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0061] It is assumed that in Rel. 17 NR and later, the MAC CE / DCI supports beam activation / indication to a TCI state associated with a different physical cell identifier (PCI), and in Rel. 18 NR and later, the MAC CE / DCI supports indicating a serving cell change to a cell with a different PCI.

[0062] (TCI State Indication) The Rel. 17 unified TCI framework supports the following modes 1 to 3: [Mode 1] MAC CE based TCI state indication [Mode 2] DCI based TCI state indication by DCI format 1_1 / 1_2 with DL assignment [Mode 3] DCI based TCI state indication by DCI format 1_1 / 1_2 without DL assignment

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

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

[0065] In Rel. 15 / 16, if a UE does not support active BWP changes via DCI, the UE ignores the BWP indicator field. A similar behavior is considered for the relationship between support for Rel. 17 TCI states and the interpretation of the TCI field. It is considered that if a UE is configured with Rel. 17 TCI states, the TCI field will always be present in DCI format 1_1 / 1_2, and if the UE does not support TCI updates via DCI, the UE will ignore the TCI field.

[0066] In Rel. 15 / 16, whether or not a TCI field is present (TCI presence information in DCI, tci-PresentInDCI) is set for each CORESET.

[0067] The TCI field in DCI format 1_1 is 0-bit if the higher layer parameter tci-PresentInDCI is not enabled, and 3-bit otherwise. If the BWP indicator field indicates a BWP other than the active BWP, the UE shall follow the following behavior: [Action] If the higher layer parameter tci-PresentInDCI is not enabled for the CORESET used for the PDCCH carrying that DCI format 1_1, the UE shall assume that tci-PresentInDCI is not enabled for all CORESETs in the indicated BWP; otherwise, the UE shall assume that tci-PresentInDCI is enabled for all CORESETs in the indicated BWP.

[0068] The TCI field in DCI format 1_2 is 0 bit if the higher layer parameter tci-PresentInDCI-1-2 is not set, otherwise it is 1, 2 or 3 bits determined by the higher layer parameter tci-PresentInDCI-1-2. If the BWP indicator field indicates a BWP other than the active BWP, the UE shall follow the following actions. [Operation] If the higher layer parameter tci-PresentInDCI-1-2 is not set for the CORESET used for the PDCCH carrying that DCI format 1_2, the UE shall assume that tci-PresentInDCI is not enabled for all CORESETs in the indicated BWP; otherwise, the UE shall assume that tci-PresentInDCI-1-2 for all CORESETs in the indicated BWP is set with the same value as tci-PresentInDCI-1-2 set for the CORESET used for the PDCCH carrying that DCI format 1_2.

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

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

[0071] (Beam Application Time (BAT)) In DCI-based beam indication in Rel. 17, the following considerations 1 and 2 are considered regarding the application time of the beam / unified TCI status indication (beam application time (BAT) conditions).

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

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

[0074] For DCI-based beam direction in Rel. 17, it is considered that at least one Y symbol per BWP / CC is configured in the UE.

[0075] If the SCS is different between multiple CCs, the value of the Y symbol is also different, and therefore the application time may differ between multiple CCs.

[0076] [Consideration 2] For the CA case, the timing / BAT of applying the beam instruction may follow any of the following options 1 to 3: [Option 1] Both the first slot and Y symbol are determined on the carrier with the smallest SCS among the one or more carriers to which the beam instruction is applied. [Option 2] Both the first slot and Y symbol are determined on the carrier with the smallest SCS among the one or more carriers to which the beam instruction is applied and the UL carrier carrying the ACK. [Option 3] Both the first slot and Y symbol are determined on the UL carrier carrying the ACK.

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

[0078] The application time (Y symbols) of beam direction for CA may be determined on the carrier with the smallest SCS among the carriers to which beam direction applies. Rel. 17 MAC CE-based beam direction (when only a single TCI codepoint is activated) may follow the Rel. 16 application timeline for MAC CE activation.

[0079] Based on these considerations, the following behavior is considered to be specified in the specification: [Behavior] When a UE transmits the last symbol of a PUCCH with HARQ-ACK information corresponding to a DCI carrying a TCI state indication, the indicated TCI state with a Rel. 17 TCI state may start to apply from the first slot that is at least Y symbols after the last symbol of the PUCCH. Y may be a higher layer parameter (e.g., BeamAppTime_r17[symbols]). Both the first slot and Y symbols may be determined on the carrier with the smallest SCS among the carriers to which the beam indication applies. At a given time, the UE may assume one indicated TCI state with a Rel. 17 TCI state for both DL and UL, or one indicated TCI state with a Rel. 17 TCI state for UL (separate from DL).

[0080] X [ms] may be used instead of Y [symbols].

[0081] Regarding the application time, it is considered that the UE reports at least one of the following UE capabilities 1 and 2: [UE capability 1] Minimum application time per SCS (minimum of Y symbols between the last symbol of the PUCCH carrying ACK and the first slot in which the beam is applied). [UE capability 2] Minimum time gap between the last symbol of the beam indication PDCCH (DCI) and the first slot in which the beam is applied. The gap between the last symbol of the beam indication PDCCH (DCI) and the first slot in which the beam is applied may satisfy the UE capability (minimum time gap).

[0082] UE capability 2 may be an existing UE capability (eg, timeDurationForQCL).

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

[0084] Regarding the application time, the parameter set by the base station (eg, BeamAppTime_r17) may be an optional field.

[0085] (Indicated Rel. 17 TCI State / Configured Rel. 17 TCI State) Regarding the Rel. 17 TCI state, the unified / common TCI state may refer to the Rel. 17 TCI state indicated using (Rel. 17) DCI / MAC CE / RRC (indicated Rel. 17 TCI state). In the present disclosure, the indicated Rel. 17 TCI state, the indicated TCI state, the unified / common TCI state, and the TCI state applied to multiple types of signals (channels / RSs) may be interpreted interchangeably.

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

[0087] Regarding the Rel. 17 TCI state, a TCI state other than the unified TCI state may refer to a Rel. 17 TCI state configured using (Rel. 17) MAC CE / RRC (configured Rel. 17 TCI state). In this disclosure, the terms configured Rel. 17 TCI state, configured TCI state, TCI state other than the unified TCI state, and TCI state applied to a specific type of signal (channel / RS) may be interpreted interchangeably.

[0088] The configured Rel. 17 TCI state may not be shared with at least one of the UE-specific reception of PDSCH / PDCC (updated using Rel. 17 DCI / MAC CE / RRC), PUSCH of dynamic grant (DCI) / configured grant, and multiple (e.g., all) dedicated PUCCH resources. The configured Rel. 17 TCI state may be configured by RRC / MAC CE per CORESET / per resource / per resource set, and may not be updated even if the indicated Rel. 17 TCI state (common TCI state) is updated.

[0089] It is being considered that the indicated Rel. 17 TCI state will be applied to UE-specific channels / signals (RS), and that the UE will be notified by higher layer signaling (RRC signaling) whether the indicated Rel. 17 TCI state or the configured Rel. 17 TCI state will be applied to non-UE-specific channels / signals.

[0090] It is being considered that the RRC parameters for the configured Rel. 17 TCI state (TCI state ID) will have the same configuration as the RRC parameters for the TCI state in Rel. 15 / 16. It is also being considered that the configured Rel. 17 TCI state will be configured / instructed per CORESET / per resource / per resource set using RRC / MAC CE. It is also being considered that the UE will determine the configuration / instruction based on specific parameters.

[0091] It is considered that the UE updates the indicated TCI state and the configured TCI state separately. For example, if the unified TCI state for the indicated TCI state is updated, the UE may not update the configured TCI state. It is also considered that the UE may determine whether to update the configured TCI state based on a specific parameter.

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

[0093] Regarding intra-cell beam indication (TCI state indication), it is being considered to support Rel. 17 TCI state indication for a UE-specific CORESET and its associated PDSCH, and a non-UE-specific CORESET and its associated PDSCH.

[0094] Also, for inter-cell beam indication (e.g., L1 / L2 inter-cell mobility), it is considered that indication Rel. 17 TCI states will be supported for UE-specific CORESETs and their associated PDSCHs.

[0095] In Rel. 15, whether to indicate the TCI state for CORESET #0 was up to the implementation of the base station. In Rel. 15, for CORESET #0 for which a TCI state is indicated, the indicated TCI state is applied. For CORESET #0 for which a TCI state is not indicated, the SSB and QCL selected at the time of the latest (most recent) PRACH transmission are applied.

[0096] In the unified TCI state framework for Rel. 17 and later, the TCI state for CORESET #0 is being considered.

[0097] For example, in the unified TCI state framework for Rel. 17 and later, whether or not to apply the indicated Rel. 17 TCI state associated with the serving cell for the Rel. 17 TCI state indication in CORESET #0 is configured by RRC for each CORESET, and if not, the legacy MAC CE / RACH signaling mechanism may be used.

[0098] Note that the CSI-RS associated with the Rel. 17 TCI state applied to CORESET #0 may be QCL'd with the SSB associated with the serving cell PCI (physical cell ID) (similar to Rel. 15).

[0099] For CORESET #0, a CORESET with a common search space (CSS), and a CORESET with a CSS and a UE-specific search space (USS), whether to follow the Rel. 17 TCI state may be configured for each CORESET by an RRC parameter. If the Rel. 17 TCI state is not configured to be followed for that CORESET, the configured Rel. 17 TCI state may be applied to that CORESET.

[0100] For non-UE-dedicated channels / RSs (except CORESET), whether to follow the indicated Rel. 17 TCI state may be configured by an RRC parameter for each channel / resource / resource set. If the indicated Rel. 17 TCI state is not configured for that channel / resource / resource set, the configured Rel. 17 TCI state may apply to that channel / resource / resource set.

[0101] (Intra-cell / Inter-cell Beam Indication / Management) In Rel. 17 NR and later, it is assumed that MAC CE / DCI will support beam indication to a TCI state associated with a different PCI. Also, in Rel. 18 NR and later, it is assumed that MAC CE / DCI will support indicating a serving cell change to a cell with a different PCI.

[0102] The Rel. 17 TCI status indication may be shared (applied to) for UE-dedicated channels / RS and non-UE-dedicated channels / RS within a cell.

[0103] The Rel. 17 TCI status indication may be shared (applied) between cells for UE-specific channels / RS only.

[0104] Between cells, non-UE-dedicated channels / RSs may be configured by RRC parameters to indicate whether to follow the Rel. 17 TCI state for each PDSCH (PDSCH configuration) / CORESET (CORESET configuration). UE-dedicated channels / RSs may not follow the RRC parameters and always follow the Rel. 17 TCI state.

[0105] In the present disclosure, a non-UE-dedicated CORESET may mean a CORESET with a CSS, and a UE-dedicated CORESET may mean a CORESET with a USS. In the present disclosure, a non-UE-dedicated PDSCH may mean a PDSCH scheduled by a CORESET with a CSS, or a PDSCH scheduled by a CORESET with a CSS other than Type 3 CSS. In the present disclosure, a UE-dedicated PDSCH may mean a PDSCH scheduled by a CORESET with a USS, or a PDSCH scheduled by a CORESET with a USS or Type 3 CSS. For example, for each PDSCH configuration (PDSCH-Config), an instruction Rel. Whether or not to follow the Rel. 17 TCI state is configured by an RRC parameter (e.g., followUnifiedTCIstate), and this setting does not apply to UE-specific PDSCHs (UE-specific PDSCHs always follow the Rel. 17 TCI state), but may apply to non-UE-specific PDSCHs.

[0106] (Assuming default QCL for PDSCH) In RRC connected mode, regardless of the configuration of the presence of the TCI field in the DCI (higher layer parameters tci-PresentInDCI and tci-PresentInDCI-1-2), if the offset (time offset, scheduling offset) between the reception of a DL DCI (PDSCH scheduling DCI) and the corresponding PDSCH (PDSCH scheduled by this DCI) is smaller than a threshold (timeDurationForQCL) and at least one configured TCI state for the serving cell of that scheduled PDSCH includes a QCL type (qcl-Type) set to type D, the UE shall perform the following actions: The UE assumes that the DMRS ports of the PDSCH of the serving cell are QCLed to the RS(s) for the QCL parameters used for PDCCH quasi co-location (QCL) indication on the CORESET associated with the monitored search space, where one or more CORESETs in the active BWP of the serving cell are QCLed with the CORESET with the lowest CORESET-ID (controlResourceSetId) in the latest slot monitored by the UE (default QCL assumption / default TCI state for PDSCH (Figure 4)).

[0107] If a PDCCH carrying a scheduling DCI is received on one CC and the PDSCH scheduled by that DCI is on another CC and the UE is configured with enableDefaultBeamForCCS, and the offset between the reception of the DL DCI and the corresponding PDSCH is less than a threshold (timeDurationForQCL) or the DL DCI does not have a TCI field present, the UE shall derive the QCL assumption for the scheduled PDSCH from the active TCI state with the lowest ID among the active TCI states applicable to the PDSCH in the active BWP of the scheduled cell.

[0108] Before decoding the DL DCI, the UE does not know whether a PDSCH is scheduled or not, so the UE should buffer the DL signal using a certain QCL assumption. Three default QCL assumptions (for single TRP, for single DCI-based multi-TRP, and for multi-DCI multi-TRP) are specified in Rel. 15 / 16, and they can be switched by RRC.

[0109] (Channels / RSs to which the indicated TCI state applies) The indicated TCI state by the MAC CE / DCI may apply to the following channels / RSs:

[0110] [PDCCH] - If followUnifiedTCIState is configured for CORESET0, the indicated TCI state applies. Otherwise, the Rel. 15 specifications apply for that CORESET. That is, CORESET0 follows the TCI state activated by the MAC CE or is QCL'd with SSB. - For CORESETs other than index 0 with USS / CSS type 3, the indicated TCI state always applies. - For CORESETs other than index 0 with at least a CSS other than CSS type 3, if followUnifiedTCIState is configured, the indicated TCI state applies. Otherwise, the configured TCI state for that CORESET applies to that CORESET.

[0111] [PDSCH] - The indicated TCI state is always applied to all UE-dedicated PDSCHs. - If a non-UE-dedicated PDSCH (a PDSCH scheduled by a DCI in the CSS) is configured to follow the unified TCI state, the indicated TCI state may be applied. Otherwise, the configured TCI state for that PDSCH applies to that PDSCH. A PDSCH may not be configured to follow the unified TCI state. In this case, whether a non-UE-dedicated PDSCH follows the indicated TCI state may be determined depending on whether the CORESET used to schedule that PDSCH is configured to follow the unified TCI state.

[0112] [CSI-RS] - For A-CSI-RS for CSI acquisition or beam management, if configured to follow the unified TCI state, the indicated TCI state applies. For other CSI-RS, the configured TCI state for that CSI-RS applies.

[0113] [PUCCH] - For all dedicated PUCCH resources, the indicated TCI state always applies.

[0114] [PUSCH] - For dynamic / configured grant PUSCH, the indication TCI state always applies.

[0115] [SRS] - When the SRS resource set for the A-SRS used for beam management and the A / SP / P-SRS used for codebook / non-codebook / antenna switching is configured to follow the unified TCI state, the indicated TCI state is applied. For other SRSs, the configured TCI state in the SRS resource set is applied.

[0116] However, the relationship between the PDSCH and the unified TCI state / indicated TCI state is not clear, which may lead to a decrease in communication quality, a decrease in throughput, etc.

[0117] Therefore, the present inventors came up with a method for determining the QCL assumption.

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

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

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

[0121] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, 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.

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

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

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

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

[0126] 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 The terms 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, reference signal for QCL, UL transmit (TX) spatial filter, etc. may be read as interchangeable.

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

[0128] In this disclosure, the notation "Rel. XX" indicates a 3GPP release. However, the release number "XX" is an example and may be replaced with another number.

[0129] In the present disclosure, the terms “search space” and “search space set” may be interchangeable. In the present disclosure, the terms “type x CSS,” “type x-PDCCH CSS,” and “type x-PDCCH CSS set” may be interchangeable.

[0130] In the present disclosure, the quasi co-location (QCL) assumption of a DMRS port of a PDSCH, an RS that is QCLed (quasi co-located) with a DMRS port of a PDSCH, and the QCL assumption / TCI state of a PDSCH may be read interchangeably.

[0131] (Wireless communication method) In each embodiment, a UE-dedicated PDSCH and a PDSCH scheduled by DCI in a USS or a type 3 CSS may be interchangeable. In each embodiment, a non-UE-dedicated PDSCH and a PDSCH scheduled by DCI in a CSS other than a type 3 CSS may be interchangeable.

[0132] In each embodiment, the following may be interpreted interchangeably: the PDSCH (UE-individual PDSCH / non-UE-individual PDSCH) conforms to the unified TCI state; the CORESET used for scheduling the PDSCH conforms to the unified TCI state; in the configuration (ControlResourceSet) of the CORESET, following the unified TCI state / indicated TCI state (followUnifiedTCIState) is set; and in the configuration (PDSCH-Config) of the PDSCH, following the unified TCI state / indicated TCI state (followUnifiedTCIState) is set.

[0133] In each embodiment, a PCI different from the serving cell PCI, a non-serving cell PCI, and a non-serving cell may be read as interchangeable.

[0134] <Embodiment #1> This embodiment relates to QCL assumptions for UE-dedicated PDSCH (PDSCH scheduled by DCI in USS or type 3 CSS).

[0135] The QCL assumption for the UE-dedicated PDSCH may be an indicated TCI state. The indicated TCI state may be applied to the QCL assumption for the UE-dedicated PDSCH both in the case where the indicated TCI state is associated with the serving cell PCI and in the case where the indicated TCI state is associated with a PCI different from the serving cell PCI.

[0136] It may be assumed that the PDSCH is always set to followUnifiedTCIState in CORESET for scheduling or in the PDSCH configuration. If followUnifiedTCIState is set in CORESET for scheduling or in the PDSCH configuration, the QCL assumption for the PDSCH may be the indicated TCI state.

[0137] According to this embodiment, the UE can appropriately determine the QCL estimate for the UE-dedicated PDSCH.

[0138] <Embodiment #2> This embodiment relates to QCL assumptions for non-UE-dedicated PDSCH (PDSCH scheduled by DCI in a CSS other than Type 3 CSS).

[0139] <<Embodiment #2-1>> When a non-UE dedicated PDSCH is configured to follow the unified TCI state in CORESET for scheduling or in the PDSCH configuration, the QCL assumption for that PDSCH may be the indicated TCI state.

[0140] If the indicated TCI state is associated with the serving cell PCI, no problem occurs.

[0141] It may be specified that if the indication TCI state is associated with a PCI different from the serving cell PCI, the UE is not required (or expected) to receive that non-UE dedicated PDSCH.

[0142] It is considered that the indication TCI state associated with a PCI different from the serving cell PCI is not applicable to non-UE dedicated PDCCH / PDSCH.

[0143] It may be specified that if the CORESET for scheduling or the PDSCH configuration is configured to follow the unified TCI state, the UE does not expect to be instructed on the indicated TCI state that applies to a non-UE dedicated PDSCH (a PDSCH scheduled by a DCI in a CSS other than a type 3 CSS) and that is associated with a PCI different from the serving cell PCI.

[0144] It may be specified that if the CORESET or PDSCH configuration for scheduling is configured to follow the unified TCI state and the UE is instructed to an indicated TCI state associated with a PCI different from the serving cell PCI, the UE shall not assume that a non-UE dedicated PDSCH (a PDSCH scheduled by a DCI in a CSS other than a type 3 CSS) is scheduled.

[0145] It may be specified that if the CORESET or PDSCH configuration for scheduling is configured to follow the unified TCI state and the UE is instructed to an indicated TCI state associated with a PCI different from the serving cell PCI, the UE is not required to receive a non-UE dedicated PDSCH (a PDSCH scheduled by a DCI in a CSS other than a type 3 CSS).

[0146] It may be specified that if a UE is configured with at least one TCI state associated with a PCI different from the serving cell PCI, the UE shall not be expected to be instructed to indicate a TCI state that applies to a non-UE dedicated PDSCH (a PDSCH scheduled by a DCI in a CSS other than a type 3 CSS).

[0147] <<Embodiment #2-2>> For a non-UE dedicated PDSCH, if the unified TCI state is not configured in CORESET for scheduling or in the PDSCH configuration, the QCL assumption for that PDSCH may be the configured TCI state. The configured TCI state may be in accordance with either of the following embodiments #2-2-1 and #2-2-2.

[0148] [Embodiment #2-2-1] The RRC IE / MAC CE may set / indicate the CORESET for scheduling or the TCI state for PDSCH configuration. If the TCI state is set / indicated, the QCL assumption of the non-UE dedicated PDSCH may be the same as the configured TCI state. If the configured TCI state is set to CORESET, the QCL assumption of the PDSCH may be derived from the QCL assumption of the scheduling CORESET for that PDSCH.

[0149] [Embodiment #2-2-2] The RRC IE / MAC CE may configure / indicate multiple (active) TCI states for the CORESET for scheduling or PDSCH configuration. If multiple TCI states are configured / indicated, the QCL assumption for the non-UE dedicated PDSCH may be selected from the multiple configured TCI states. For example, the scheduling DCI for the PDSCH may indicate one of the multiple configured TCI states by the TCI field. The list of multiple configured TCI states may be the same as or different from the TCI state list / pool for the unified TCI state.

[0150] 5A shows an example of the operation of embodiment #2-2-2 when the CORESET for scheduling or the PDSCH configuration for a non-UE dedicated PDSCH is not configured to follow the unified TCI state. The DCI scheduling the non-UE dedicated PDSCH indicates TCI state #1 among multiple configured TCI states. The TCI state #1 is applied to the PDSCH. In embodiment #2-2-1, the TCI state of the PDSCH may be one configured TCI state configured / indicated by the RRC IE / MAC CE, or may be the same TCI state as the scheduling CORESET.

[0151] 5B shows an example of operation when a non-UE dedicated PDSCH is configured to follow the unified TCI state in the CORESET for scheduling or PDSCH configuration. The DCI scheduling the non-UE dedicated PDSCH indicates common beam (unified TCI state) TCI state #2. If the start timing of the PDSCH is before the application timing of the beam indication (if the beam application time condition is not met), the TCI state of the PDSCH is the previously indicated TCI state.

[0152] According to this embodiment, the UE can appropriately determine the QCL assumption for the non-UE dedicated PDSCH.

[0153] <Embodiment #3> This embodiment relates to a default QCL assumption for PDSCH.

[0154] <<Embodiment #3-1>> When a PDSCH (both a UE-dedicated PDSCH and a non-UE-dedicated PDSCH) is configured to follow the unified TCI state in CORESET for scheduling or in the PDSCH configuration, the QCL assumption for that PDSCH may be the indicated TCI state.

[0155] In this case, there is no need to specify a QCL assumption (default QCL assumption) for the case where the scheduling offset (the time offset between the reception of the DL DCI and the corresponding PDSCH scheduled thereby) is smaller than a threshold (e.g., timeDurationForQCL).

[0156] As described in embodiment #2, if the indication TCI state is associated with a non-serving cell PCI (a PCI different from the serving cell PCI), it is difficult for the UE to receive the non-UE dedicated PDSCH. To enable the UE to receive the non-UE dedicated PDSCH from the serving cell, it is preferable that the base station updates the indication TCI state associated with the serving cell PCI.

[0157] <<Embodiment #3-2>> When a UE-dedicated PDSCH is not configured to follow the unified TCI state in CORESET for scheduling or in the PDSCH configuration, the QCL assumption for the UE-dedicated PDSCH may be the indicated TCI state.

[0158] For a non-UE dedicated PDSCH, if CORESET for scheduling or PDSCH configuration is not configured to follow the unified TCI state, the QCL assumption for that non-UE dedicated PDSCH may be the configured TCI state.

[0159] In this case, the UE does not know whether the scheduling DCI is in the USS or the Type 3 CSS (whether the search space associated with the CORESET of the scheduling DCI is in the USS or the Type 3 CSS) before completing decoding of the scheduling DCI. In other words, the UE does not know whether the scheduled PDSCH is a UE-dedicated PDSCH before completing decoding of the scheduling DCI. In this case, the default QCL assumption needs to be taken into account.

[0160] The default QCL assumption may be either of the following embodiments #3-2-1 and #3-2-2.

[0161] [Embodiment #3-2-1] The default QCL assumption may be defined as an indicated TCI state in the Rel. 17 unified TCI state.

[0162] If the indication TCI state is associated with the serving cell PCI, there may be no restriction on receiving the PDSCH.

[0163] If the indicated TCI state is associated with a PCI different from the serving cell PCI, the UE may follow either of the following actions 1A and 1B. [[Action 1A]] If the scheduling offset is smaller than a threshold, the UE is not required to receive the PDSCH (regardless of whether it is a UE-dedicated PDSCH or a non-UE-dedicated PDSCH). In other words, the base station preferably schedules a PDSCH whose scheduling offset is equal to or greater than a threshold. [[Action 1B]] If the scheduling offset is smaller than a threshold, the UE is not required to receive a non-UE-dedicated PDSCH. The base station preferably schedules a non-UE-dedicated PDSCH whose scheduling offset is equal to or greater than a threshold.

[0164] [Embodiment #3-2-2] The default QCL assumption may be the same as the default QCL assumption of Rel. 15 / 16. The UE may determine the default QCL assumption in the same way as in Rel. 15 / 16.

[0165] If the determined default QCL assumption is associated with the serving cell PCI, there may be no restrictions on receiving the PDSCH.

[0166] If the determined default QCL assumption is associated with a PCI different from the serving cell PCI, the UE may follow either of the following actions 2A and 2B. [[Action 2A]] If the scheduling offset is smaller than a threshold, the UE is not required to receive the PDSCH (regardless of whether it is a UE-dedicated PDSCH or a non-UE-dedicated PDSCH). In other words, the base station preferably schedules a PDSCH whose scheduling offset is equal to or greater than a threshold. [[Action 2B]] If the scheduling offset is smaller than a threshold, the UE is not required to receive a non-UE-dedicated PDSCH. The base station preferably schedules a non-UE-dedicated PDSCH whose scheduling offset is equal to or greater than a threshold.

[0167] It may be specified that the UE does not assume that the default QCL assumption is associated with a PCI different from the serving cell PCI. Preferably, the base station sets the TCI state associated with the serving cell PCI to the lowest CORESET-ID in the latest monitoring slot.

[0168] According to this embodiment, the UE can appropriately determine the default QCL assumption for the PDSCH.

[0169] <Variation of Embodiment #3> This embodiment relates to a default QCL assumption for PDSCH.

[0170] The reason why a default QCL assumption for the PDSCH was specified in Rel. 15 is that the UE needs to receive the PDSCH before completing decoding of the DCI of the scheduling PDCCH and buffer the received signal using a certain QCL assumption. In Rel. 17, the indication TCI state applies after the beam application time from the last symbol of the corresponding HARQ-ACK information. This timing is obviously after completing decoding of the DCI scheduling the PDSCH.

[0171] <Embodiment #3a-1> If "followUnifiedTCIState" is configured, the default QCL assumption may not be considered. In this case, the QCL assumption of the PDSCH may always be the indicated TCI state, regardless of whether the PDSCH is UE-specific or not. If the indicated TCI state is associated with a PCI different from the serving cell PCI, the UE may not be required to receive a PDSCH scheduled by a CORESET with a CSS other than Type 3 CSS (non-UE-specific PDSCH).

[0172] If the PDSCH (or the CORESET for scheduling that PDSCH) is configured to follow the unified TCI state, the indicated TCI state may always be applied to the PDSCH. If the indicated TCI state is associated with a PCI different from the serving cell PCI, it may be specified that the UE is not required to receive PDSCHs scheduled by a CORESET with a CSS other than Type 3 CSS (non-UE dedicated PDSCHs).

[0173] <Embodiment #3a-2> If the unified TCI state is not configured, the QCL assumption of the PDSCH may be determined depending on whether it is UE-specific or not. Before completing DCI decoding, it is difficult for the UE to identify whether the PDSCH scheduled by that DCI is UE-specific or not (i.e., whether the search space associated with the CORESET of that DCI is Type 3 CSS or not). Therefore, it is necessary to specify a QCL assumption for receiving the PDSCH before completing DCI decoding. The QCL assumption may follow any of the following options 1 to 3.

[0174] [Option 1] The default QCL assumption for PDSCH in Rel. 15 / 16 may be reused as the QCL assumption. Since non-UE dedicated PDSCHs may be shared with Rel. 15 / 16, it is preferable to have the same QCL assumption. On the other hand, most base station operations in Rel. 15 / 16 are self-slot scheduling (scheduling PDCCH and scheduled PDSCH are in the same slot, scheduling offset is smaller than timeDurationForQCL). Therefore, this option means that the default QCL assumption in Rel. 15 / 16 is applied to PDSCHs in most cases unless the unified TCI state is configured to be followed.

[0175] [Option 2] The indicated TCI state may be applied as the QCL assumption. It may be inappropriate to apply the indicated TCI state when the unified TCI state is not configured to be followed. It is also considered that the indicated TCI state associated with a PCI different from the serving cell PCI cannot be applied to the non-UE dedicated PDCCH / PDSCH. Therefore, the non-UE dedicated PDSCH may be scheduled with a scheduling offset equal to or greater than timeDurationForQCL.

[0176] If the PDSCH (or the CORESET for scheduling that PDSCH) is not configured to follow the unified TCI state, it may be specified that if the scheduling offset is smaller than timeDurationForQCL, the UE is not required to receive a PDSCH scheduled by a CORESET with a CSS other than Type 3 CSS (non-UE dedicated PDSCH).

[0177] [Option 3] The configured TCI state may be applied as the QCL assumption. If the scheduling offset is equal to or greater than timeDurationForQCL, the configured TCI state may be applied to the non-UE dedicated PDSCH. If the scheduling offset is smaller than timeDurationForQCL, the configured TCI state may be applied to the PDSCH (UE-dedicated PDSCH and non-UE-dedicated PDSCH). The configured TCI state is intended to configure the non-UE dedicated PDSCH from the serving cell, and if the scheduling offset is smaller than timeDurationForQCL, in option 3, the non-UE dedicated PDSCH / UE-dedicated PDSCH from the non-serving cell may not be able to be scheduled.

[0178] The indication TCI state may apply to PDSCH scheduled by USS or CORESET with Type 3 CSS (UE dedicated PDSCH) if the PDSCH is scheduled with a scheduling offset equal to or greater than timeDurationForQCL.

[0179] <Supplementary Information> <UE Capability Information / Higher Layer Parameters> At least one of the above-described embodiments may be applied only to UEs that have reported or support a specific UE capability.

[0180] The specific UE capability may indicate at least one of the following: Supporting processing / operation / control / information for at least one of the above embodiments. Supporting default QCL assumption for unified TCI state / indicated TCI state. Corresponding UE capability reporting / RRC parameter configuration may apply to at least one of a UE-dedicated PDSCH and a non-UE-dedicated PDSCH. Corresponding UE capability reporting / RRC parameter configuration may apply to at least one of a PDSCH using a TCI state associated with the serving cell PCI and a PDSCH using a TCI state associated with a PCI different from the serving cell PCI. Supporting QCL assumption / TCI state of PDSCH / UE-dedicated PDSCH / non-UE-dedicated PDSCH being the indicated TCI state (unified TCI state). Supporting default QCL assumption of PDSCH / UE-dedicated PDSCH / non-UE-dedicated PDSCH being the indicated TCI state (unified TCI state).

[0181] Furthermore, the specific UE capability may be a capability that is applied across all frequencies (commonly regardless of frequency), or may be a capability for each frequency (e.g., cell, band, BWP), or may be a capability for each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or may be a capability for each subcarrier spacing (SubCarrier Spacing (SCS)).

[0182] Furthermore, the specific UE capability may be a capability that is applied to all duplexing methods (commonly regardless of the duplexing method), or may be a capability for each duplexing method (e.g., Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

[0183] Furthermore, at least one of the above-described embodiments may be applied when specific information related to the above-described embodiments is configured in the UE by higher layer signaling. For example, the specific information may be information indicating that at least one feature of the above-described embodiments is enabled, any RRC parameter for a specific release (e.g., Rel. 18), etc. The RRC parameter may be named with _r18.

[0184] If the UE does not support at least one of the specific UE capabilities or is not configured with the specific information, the UE may apply, for example, Rel. 15 / 16 behavior.

[0185] The above UE capabilities / higher layer parameters allow the UE to achieve the above functions while maintaining compatibility with existing specifications.

[0186] (Supplementary Notes) The following inventions are supplementary notes regarding one embodiment of the present disclosure. [Supplementary Note 1] A terminal comprising: a receiver unit that receives a configuration indicating whether scheduling of a physical downlink shared channel (PDSCH) follows a specific transmission configuration indication (TCI) state applied to multiple types of signals, either downlink and uplink, and downlink; and a controller that determines a quasi co-location (QCL) assumption for a demodulation reference signal (DMRS) port of the PDSCH based on the configuration. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the PDSCH is scheduled by downlink control information in a user equipment (UE)-specific search space set or a Type 3 Physical Downlink Control Channel (PDCCH) Common Search Space (CSS) set. [Supplementary Note 3] The terminal according to Supplementary Note 1, wherein the PDSCH is scheduled by downlink control information in a CSS set other than a Type 3 PDCCH CSS set. [Supplementary Note 4] The terminal according to any one of Supplementary Notes 1 to 3, wherein the terminal uses the specific TCI state as the QCL assumption if the scheduling does not follow the specific TCI state and if a time offset between downlink control information scheduling the PDSCH and the PDSCH is smaller than a threshold.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0230] The transceiver 120 may transmit a configuration indicating whether scheduling of a physical downlink shared channel (PDSCH) follows a specific transmission configuration indication (TCI) state that applies to multiple types of signals, including downlink and uplink, and the control unit 110 may determine a quasi co-location (QCL) assumption for a demodulation reference signal (DMRS) port of the PDSCH based on the configuration.

[0231] (User Terminal) Fig. 8 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 may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0248] The transceiver 220 may receive a configuration (CORESET configuration (ControlResourceSet) / PDSCH configuration (PDSCH-Config)) indicating whether scheduling of a physical downlink shared channel (PDSCH) follows a specific transmission configuration indication (TCI) state (indicated TCI state / uniform TCI state) applied to multiple types of signals in the downlink and uplink. The control unit 210 may determine a quasi co-location (QCL) assumption for a demodulation reference signal (DMRS) port of the PDSCH based on the configuration.

[0249] The PDSCH may be scheduled by downlink control information within a user equipment (UE) specific search space set or a Type 3 Physical Downlink Control Channel (PDCCH) Common Search Space (CSS) set.

[0250] The PDSCH may be scheduled by downlink control information in a CSS set other than the Type 3-PDCCH CSS set.

[0251] If the scheduling does not follow the specific TCI state and the time offset between the downlink control information scheduling the PDSCH and the PDSCH is less than a threshold, the specific TCI state may be used as the QCL assumption.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0301] In the present disclosure, a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control / operate based on the information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0336] In the present disclosure, terms such as "less than or equal to," "less than," "greater than," "more than," "equal to," etc. may be interchangeable. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative, as expressions with "i-th" (i is an arbitrary integer) attached (for example, "highest" may be interchangeable with "i-th highest").

[0337] In this disclosure, the terms "of," "for," "regarding," "related to," "associated with," etc. may be read interchangeably.

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

Claims

1. A receiving unit for receiving a Medium Access Control control element (MAC CE) indicating a plurality of transmission configuration indication (TCI) states for a control resource set (CORESET) for scheduling a Physical Downlink Shared Channel (PDSCH); A control unit that applies one of the multiple TCI states to a quasi co-location (QCL) assumption of a demodulation reference signal (DMRS) port of the PDSCH when a parameter indicating that the unified TCI state is followed is not set for the CORESET.

2. The terminal described in claim 1, wherein the list of the plurality of TCI states is different from the list of the unified TCI states.

3. receiving a Medium Access Control control element (MAC CE) indicating a plurality of Transmission Configuration Indication (TCI) states for a control resource set (CORESET) for scheduling a Physical Downlink Shared Channel (PDSCH); and applying one of the plurality of TCI states to a quasi co-location (QCL) assumption of a demodulation reference signal (DMRS) port of the PDSCH when a parameter indicating that a unified TCI state is followed is not set for the CORESET.

4. A transmitter for transmitting a Medium Access Control control element (MAC CE) indicating a plurality of transmission configuration indication (TCI) states for a control resource set (CORESET) for scheduling a physical downlink shared channel (PDSCH); A base station having a control unit that applies one of the multiple TCI states to a quasi co-location (QCL) assumption of a demodulation reference signal (DMRS) port of the PDSCH when a parameter indicating that a unified TCI state is followed is not set for the CORESET.

5. A system including a terminal and a base station, The terminal includes: A receiving unit for receiving a Medium Access Control control element (MAC CE) indicating a plurality of transmission configuration indication (TCI) states for a control resource set (CORESET) for scheduling a Physical Downlink Shared Channel (PDSCH); A control unit that applies one of the plurality of TCI states to a quasi co-location (QCL) assumption of a demodulation reference signal (DMRS) port of the PDSCH when a parameter indicating that a unified TCI state is followed is not set for the CORESET, The base station, A system comprising a transmitter for transmitting the MAC CE.