Terminal, radio communication method, and base station

Abstract

To improve communication quality / throughput.SOLUTION: A terminal according to an aspect of the present disclosure has: a receiving unit that receives settings indicating an integrated TCI state list; and a control unit that, when a physical downlink shared channel (PDSCH) of a serving cell is scheduled by a physical downlink control channel (PDCCH) in a control resource set not conforming to the integrated TCI state, and when a condition that the time offset between the PDCCH and the PDSCH is equal to or more than a threshold cannot be applied, applies the indicated TCI state in the integrated TCI state list to reception of the PDSCH.SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

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

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

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

[0005] In existing wireless communication systems (e.g., NR), it is being considered that a unified transmission configuration indication (TCI) state be applied to the reception and transmission of channels or signals.

[0006] However, the behavior regarding such TCI states has not been fully considered. If the TCI states are not applied appropriately, there is a risk that communication quality / throughput will be degraded.

[0007] Therefore, one object of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can improve communication performance / throughput. [Means for solving the problem]

[0008] A terminal according to one embodiment of the present disclosure includes: a receiving unit that receives a configuration indicating a unified TCI state list; and a control unit that applies an indicated TCI state in the unified TCI state list to reception of a physical downlink shared channel (PDSCH) of a serving cell when the PDSCH is scheduled by a physical downlink control channel (PDCCH) in a control resource set that does not comply with the unified TCI state and when a condition that a time offset between the PDCCH and the PDSCH is greater than or equal to a threshold cannot be applied. [Effects of the Invention]

[0009] According to one aspect of the present disclosure, communication quality / throughput can be improved. [Brief explanation of the drawings]

[0010] [Figure 1] 1A and 1B show an example of determining the QCL assumption for PDSCH. [Figure 2] FIG. 2 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment of the present disclosure. [Figure 3] FIG. 3 is a diagram illustrating an example of a configuration of a base station according to an embodiment of the present disclosure. [Figure 4] FIG. 4 is a diagram illustrating an example of a configuration of a terminal according to an embodiment of the present disclosure. [Figure 5] FIG. 5 is a diagram illustrating an example of a hardware configuration of a base station and a terminal according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

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

[0012] One beam for both DL and UL (one joint TCI state) or one beam for DL ​​and one for UL (two separate TCI states, DL TCI state and UL TCI state) are considered.

[0013] The unified TCI framework supports modes 1 to 3 below. 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

[0014] Note that the DCI in the above Mode 2 / Mode 3 may also be referred to as beam indication DCI.

[0015] In the present disclosure, the TCI state indicated by DCI, the indicated TCI state, the Indicated TCI state, the indicated TCI-State, the unified TCI state, the TCI state according to the unified TCI state, the TCI state applied to multiple types of channels / signals, the joint TCI state for DL and UL, the DL TCI state, the UL TCI state, the Rel.17 TCI state, the common TCI state, the single unified TCI state to be set, the single unified TCI state to be activated, may be read as each other.

[0016] In the present disclosure, the TCI state set by RRC parameters, the set TCI state, the configured TCI state, the set TCI-State, the TCI state not according to the unified TCI state, the TCI state other than the unified TCI state, the TCI state / space relationship set for a specific channel / signal, the individual TCI state, may be read as each other.

[0017] <Application of the indicated TCI state in Rel.17> The indicated TCI state ("indicated TCI state") by MAC CE / DCI may be applied to the following channels / RSs.

[0018] < <pdcch>> One TCI state applied to the PDCCH may be based on: ◆If followUnifiedTCIState is set for CORESET0, the indicated TCI state applies. Otherwise, the Rel.15 specification applies for that CORESET. That is, CORESET0 follows the TCI state activated by the MAC CE or is quasi co-located (QCL) with SSB. ◆The indication TCI state always applies for a CORESET other than index 0 that includes at least one of a UE-specific search space (USS) [set] and a type 3-PDCCH common search space (CSS) [set]. ◆ If a CORESET with index other than 0 and with at least a CSS[set] of type 3-PDCCH CSS[set] is configured to follow the unified TCI state, the indicated TCI state applies. Otherwise, the configured TCI state for that CORESET applies to that CORESET.

[0019] < <pdsch>> One TCI state applied to the PDSCH may be based on: ◆The indication TCI state always applies to all UE-dedicated PDSCHs. For a non-UE-dedicated PDSCH (a PDSCH scheduled by a DCI in a CSS [set]), if followUnifiedTCIState is configured [for the CORESET of the PDCCH that schedules that PDSCH], the indicated TCI state may be applied. Otherwise, the configured TCI state for that PDSCH applies to that PDSCH. In other words, whether a non-UE-dedicated PDSCH follows the indicated TCI state may be determined depending on whether followUnifiedTCIState is configured for the CORESET used to schedule that PDSCH.

[0020] < <csi-rs>> One TCI state applied to the CSI-RS may be based on: For an aperiodic (A)-CSI-RS for CSI acquisition or beam management, if followUnifiedTCIState is set [for the CORESET of the PDCCH that triggers that A-CSI-RS], the indicated TCI state applies. For other CSI-RSs, the configured TCI state for that CSI-RS applies.

[0021] < <pucch>> One TCI state applied to the PUCCH may be based on: ◆ For all dedicated PUCCH resources, the indication TCI state always applies.

[0022] < <pusch>> One TCI state applied to the PUSCH may be based on: ◆ For dynamic / configured grant PUSCH, the indicated TCI state is always applied.

[0023] < <srs>> One TCI state applied to the SRS may be based on: ◆When the SRS resource set for aperiodic (A)-SRS for beam management and A / semi-persistent (SP) / periodic (P)-SRS for codebook (CB) / non-codebook (NCB) / antenna switching is configured to follow the unified TCI state, the indicated TCI state applies. For other SRSs, the configured TCI state in the SRS resource set applies.

[0024] In the present disclosure, the indicated TCI state, the unified TCI state, the TCI state applied to channels / signals configured to follow the unified TCI state, the TCI state applied to the UE-dedicated PDSCH and the CORESET / PDCCH associated with the USS [set], and the TCI state applied to the PUCCH and PUSCH may be read as interchangeable.

[0025] <Antenna port pseudo-colocation (Rel.17)> Physical layer procedures for data: PDSCH-related procedures: UE procedures for receiving PDSCH The PDSCH antenna port quasi co-location (QCL) is based on the following procedure Dx.

[0026] ◆ Step D1: If the UE is not provided with dl-OrJointTCI-StateList-r17 (DL or Joint TCI State List), and the PDSCH is scheduled by a DCI format with the presence of a TCI field, and the TCI field in the DCI in the scheduling CC points to an activated TCI state in the scheduled CC or DL ​​BWP, the TCI-State according to the value of the 'Transmission Configuration Indication' (TCI) field in the detected PDCCH with the DCI is used to determine the PDSCH antenna port QCL. If the time offset (scheduling offset) between the reception of the DL DCI and its corresponding PDSCH is equal to or greater than a threshold timeDurationforQCL, the UE assumes that the DM-RS port of the PDSCH of the serving cell is quasi-colocated (QCLed) with one or more RSs in the TCI state for one or more QCL type parameters given by the indicated TCI state. where the threshold is based on the reported UE capability. For a single-slot PDSCH, the one or more indicated TCI states are based on one or more activated TCI states in a slot with a scheduled PDSCH. For a multi-slot PDSCH, or if the UE is configured with the higher layer parameter pdsch-TimeDomainAllocationListForMultiPDSCH, the one or more indicated TCI states are based on one or more activated TCI states in the first slot with one or more scheduled PDSCHs, and the UE expects the one or more activated TCI states to be the same across multiple slots with one or more scheduled PDSCHs.If a UE is configured with a CORESET associated with a search space set for cross-carrier scheduling and the UE does not configure enableDefaultBeamForCCS, the UE shall expect tci-PresentInDCI to be set to 'enabled' or tci-PresentDCI-1-2 to be set for that CORESET, and if one or more TCI states configured for a serving cell scheduled by that search space set include qcl-Type set to 'typeD', the UE shall expect the time offset between reception of a PDCCH detected within that search space set and its corresponding PDSCH to be greater than or equal to a threshold timeDurationforQCL.

[0027] ◆Step D2: In RRC connected mode, regardless of the configuration of tci-PresentInDCI and tci-PresentDCI-1-2, if the UE is provided with dl-OrJointTCI-StateList-r17 and the [time] offset between the reception of the DL DCI and the corresponding PDSCH is smaller than the threshold timeDurationforQCL and at least one configured TCI state for the serving cell of the scheduled PDSCH includes qcl-Type set to 'typeD', the UE procedure is based on the following step D2-x, regardless of the configuration of followUnifiedTCI-State.

[0028] - ◆ Step D2-1: If the indicated TCI state is associated with the physical cell ID (PCI) of the serving cell, the indicated TCI state is applied to PDSCH reception.

[0029] - ◆ Step D2-2: If the indicated TCI state is associated with a PCI different from that of the serving cell, the UE may assume that one or more PDSCH DM-RS ports of the serving cell are QCLed with the RS for one or more QCL parameters used in the PDCCH QCL indication of the CORESET associated with the monitored search space having the lowest controlResourceSetId (CORESET ID) in the most recent slot in one or more CORESETs in the active BWP of the serving cell monitored by the UE. In the case of carrier aggregation (CA), if the 'QCL-TypeD' of PDSCH DMRSs from each CC in a band is different within a slot, the QCL-TypeD assumption of the PDSCH DMRS in the CC with the lowest CC ID in the band applies to all PDSCH DMRSs in multiple CCs in the band. In this case, if the qcl-Type set for 'type D' of a PDSCH DMRS differs from the qcl-Type set for 'type D' of a PDCCH DMRS that overlaps with the PDSCH DMRS within at least one symbol, the UE is expected to prioritize reception of the PDCCH associated with its CORESET. This also applies to the case of intra-band CA (when the PDSCH and its CORESET are in different CCs).

[0030] ◆Step D3: Regardless of the settings of tci-PresentInDCI and tci-PresentDCI-1-2 in RRC connected mode, for a UE provided with dl-OrJointTCI-StateList-r17, if the PDSCH of the serving cell is scheduled by a CORESET that does not comply with the indicated TCI state and the time offset between the reception of the DL DCI and the corresponding PDSCH is greater than or equal to the threshold timeDurationforQCL, the indicated TCI state applies to that PDSCH of that serving cell.

[0031] <UE Procedures for PDCCH Allocation Decision (Rel.17)> Physical Layer Procedures for Control: UE Procedures for Receiving Control Information

[0032] The UE procedures for PDCCH allocation decision are based on the following multiple procedures Fx.

[0033] ◆ Procedure F1: For CORESETs other than the CORESET with index 0, the UE procedures are based on the following procedure F1-x.

[0034] ―◆ Procedure F1-1: If the UE is not provided with the setting of one or more TCI states by tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList for the CORESET, or if the UE is provided with the initial setting of more than one TCI state by tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList but does not receive the MAC CE activation command for one of the multiple TCI states, the UE assumes that the DM-RS antenna port associated with PDCCH reception is QCL with the SS / PBCH block identified by the UE during the initial access procedure, or the SS / PBCH block for the most recent configured grant PUSCH transmission for the same HARQ process.

[0035] ―◆ Procedure F1-2: If the UE is provided with the setting of more than one TCI state by tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList for the CORESET as part of the reconfiguration procedure with synchronization but does not receive the MAC CE activation command for one of the multiple TCI states, the UE assumes that the DM-RS antenna port associated with PDCCH reception is QCL with the SS / PBCH block or CSI-RS resource identified by the UE during the random access procedure started by the reconfiguration procedure with synchronization.

[0036] ◆ Procedure F2: For a CORESET with index 0, the UE procedure is based on the following procedure F2-x.

[0037] -◆Step F2-1: If the UE has been provided with a TCI-State and followUnifiedTCI-State = 'enabled' for that CORESET, the UE assumes that the DM-RS antenna ports for one or more PDCCH receptions in that CORESET and the DM-RS antenna ports for one or more PDSCH receptions scheduled by one or more DCI formats provided by one or more PDCCH receptions in that CORESET are QCL'd with the reference signal provided by the indicated TCI-State.

[0038] - ◆ Step F2-2: Otherwise, the UE assumes that one or more DM-RS antenna ports for PDCCH reception in its CORESET are QCL'd with one of the following multiple signals x: - - ◆ Signal 1: One or more DL RSs configured according to the TCI state indicated by the MAC CE activation command for that CORESET. --◆Signal 2: SS / PBCH block identified by the UE during the most recent random access procedure that was not initiated by a PDCCH order triggering a contention-free random access procedure, or SS / PBCH block identified by the UE during the most recent configuration grant PUSCH transmission, when no MAC CE activation command indicating the TCI state for that CORESET has been received after the most recent random access procedure.

[0039] ◆ Step F3: If the UE is provided with a TCI-State in the dl-OrJointTCI-StateList, the DM-RS antenna ports for one or more PDCCH receptions in the CORESET that are associated with at least one of one or more USS sets and one or more Type 3-PDCCH CSS sets other than the CORESET with index 0, and the DM-RS antenna ports for one or more PDSCH receptions scheduled by one or more DCI formats provided by one or more PDCCH receptions in that CORESET are QCL'd with the reference signal provided by the indicated TCI-State.

[0040] ◆ Step F4: If the UE is provided with a followUnifiedTCI-State for a CORESET that is associated with at least one CSS set other than the Type 3-PDCCH CSS set other than the CORESET with index 0, the DM-RS antenna ports for one or more PDCCH receptions in that CORESET and the DM-RS antenna ports for one or more PDSCH receptions scheduled by one or more DCI formats provided by one or more PDCCH receptions in that CORESET are QCL'd with the reference signal provided by the indicated TCI-State.

[0041] (analysis) For the aforementioned step D3 (when the UE is provided with dl-OrJointTCI-StateList-r17), for beam determination for PDSCH reception in FR1, it is considered that the UE determines timeDurationForQCL in FR1 to be 0 and performs the beam determination procedure by ignoring the condition that the UE uses timeDurationForQCL.

[0042] The existing specification (Determining PDSCH QCL assumptions, step D3) is unclear when the UE capability for timeDurationForQCL is not reported [within FR1], especially when the scheduling CORESET does not follow the unified TCI state. Also, step D1 in the Rel. 15 TCI framework (Determining PDSCH QCL assumptions when the UE is not provided with dl-OrJointTCI-StateList-r17) is unclear. A lack of clarity in the specification could result in reduced communication quality / throughput.

[0043] Therefore, the present inventors came up with the idea of ​​a method for determining an assumed QCL for PDSCH.

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

[0045] (Various reading changes) In this disclosure, words enclosed in "()" in a sentence may indicate an explanation of the immediately preceding wording (for example, an explanation of spelling), a paraphrase, a specific example, a supplementary explanation, etc. Also, in this disclosure, words enclosed in "[ ]" in a sentence may be interpreted including the meaning of the entire sentence, or may be interpreted excluding the meaning of the entire sentence (ignoring the meaning of the entire sentence). Note that "()" and "[ ]" may also be used for purposes / meanings other than those mentioned above.

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

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

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

[0049] In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., messages from the core network such as positioning protocol (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP)) messages), or a combination thereof.

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

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

[0052] In the present disclosure, ceil(x), ceiling function, and ceiling function may be interchangeable. In the present disclosure, floor(x), floor function, and floor function may be interchangeable. In the present disclosure, ceil(x) and floor(x) may be interchangeable. In the present disclosure, sqrt(x), square root of x, and root x may be interchangeable. In the present disclosure, x mod y, mod(x,y), mod function, and modulo operation may be interchangeable. In the present disclosure, Σ i=M M+N-1 f(i),Σ i=M M+N-1 f i , f(i) or f for i=M, M+1,..., M+N-1 i summation of f(M)+f(M+1)+...+f(M+N-1), f M +f M+1 +...+f M+N-1 , may be read interchangeably. C(n,k) is the number of combinations of k values ​​selected from n values ​​(combinatorial coefficient), binomial coefficients, n C k , C n k , may be read as interchangeable. In the present disclosure, x / / y and floor(x / y) may be read as interchangeable.

[0053] In this disclosure, A b , A_b, Ab, and A with b added to the bottom right may be read interchangeably. c , A^c, and the notation of A with c added to the upper right may be read interchangeably. b c , A_b^c, and the notation in which b is added to the bottom right of A and c is added to the top right of A may be read interchangeably. ~ may be expressed by adding 〜 to the x, or may be referred to as x tilde. - may be represented by placing a - on top of the x, or may be referred to as an x-bar. ^ may be represented by placing a ^ above the x, or may be called an x-hat.

[0054] In the present disclosure, FR may be, for example, at least one of FR1, FR2, FR2-1, FR2-2, FR3, sub-terahertz, and terahertz. In the present disclosure, the frequency range corresponding to FR1 may be 410-7125 MHz. In the present disclosure, FR2 may include FR2-1 and FR2-2, and the frequency range corresponding to FR2-1 may be 24250-52600 MHz, and the frequency range corresponding to FR2-1 may be 52600-71000 MHz.

[0055] (Wireless communication method) In the present disclosure, the terms QCL [assumed] [applied to PDSCH], TCI state, one or more RSs in the TCI state related to one or more QCL type parameters provided by the TCI state, RS related to the QCL parameters used in the QCL indication, reference signal provided by the TCI-State, one or more DL RSs configured by the TCI state, DL RS, SS / PBCH block, and CSI-RS resource may be read as interchangeable terms.

[0056] In this disclosure, the DL or joint TCI state list (dl-OrJointTCI-StateList-r17) is provided / configured, and the [Rel.17] unified TCI framework may be interchangeable. In this disclosure, the DL or joint TCI state list (dl-OrJointTCI-StateList-r17) and the configuration indicating the unified TCI state list may be interchangeable.

[0057] In the present disclosure, the DL or joint TCI state list (dl-OrJointTCI-StateList-r17) is provided / configured, and the Rel. 15 TCI framework may be read interchangeably.

[0058] In the present disclosure, non-serving cell, non-serving cell physical cell ID (PCI) [cell corresponding to], PCI [cell corresponding to] different PCI from the serving cell [PCI], additional PCI [cell corresponding to], neighboring cell, and candidate cell may be interpreted as interchangeable.

[0059] In the present disclosure, a CORESET that does not follow the indicated TCI state (unified TCI state) and a CORESET for which followUnifiedTCI-State[='enabled'] is not set may be read as interchangeable.

[0060] In the present disclosure, the expressions "a particular condition / threshold is applicable" and "a condition including the particular condition is determined" may be interpreted interchangeably. In the present disclosure, the expressions "a particular condition / threshold is not applicable" and "a condition not including the particular condition is determined" may be interpreted interchangeably.

[0061] A UE may receive a configuration indicating a unified TCI state list. [Regardless of whether a TCI field is present in DCI (tci-PresentInDCI and tci-PresentDCI-1-2 configurations) in RRC connected mode] If a physical downlink shared channel (PDSCH) of a serving cell is scheduled by a physical downlink control channel (PDCCH) in a control resource set that does not follow the unified TCI state, and the condition / threshold that the time offset between the PDCCH and the PDSCH is equal to or greater than a threshold (timeDurationforQCL) cannot be applied, the UE may apply an indicated TCI state (unified TCI state) in the unified TCI state list to receive the PDSCH [assuming a QCL for the PDSCH].

[0062] In the case where the scheduling PDCCH (CORESET) in FR1 does not follow the indicated TCI state (unified TCI state), the PDSCH reception may be based on one of the following embodiments.

[0063] <Embodiment 1> The UE / BS shall always follow the indicated TCI state when receiving a PDSCH scheduled by a PDCCH in a CORESET that does not follow the unified TCI state within FR1.

[0064] By adding "if applicable" to the PDSCH antenna port QCL procedure, it is possible to clarify that if the condition / threshold using the threshold timeDurationForQCL is applicable, the UE applies / determines that condition, and if the threshold / condition is not applicable, the UE does not apply / determine that condition, thereby clarifying that the same PDSCH QCL assumptions as those for FR2 are applicable to FR1. It is not necessary to add to step D3 that the UE in FR1 ignores the condition using timeDurationForQCL.

[0065] According to the first embodiment, the UE / BS can appropriately determine / assume the QCL assumption of the PDSCH scheduled by the PDCCH in the CORESET that does not follow the unified TCI state within the FR1.

[0066] <<<Specific examples>>> The above-described procedure D3 may be changed to the following procedure D3a.

[0067] ◆Step D3a: Regardless of the settings of tci-PresentInDCI and tci-PresentDCI-1-2 in RRC connected mode, for a UE provided with dl-OrJointTCI-StateList-r17, if the PDSCH of the serving cell is scheduled by a CORESET that does not comply with the indicated TCI state and if the condition / threshold [that the time offset between the reception of a DL DCI and the corresponding PDSCH is greater than or equal to the threshold timeDurationforQCL] is applicable, then if the time offset between the reception of a DL DCI and the corresponding PDSCH is greater than or equal to the threshold timeDurationforQCL, the indicated TCI state is applied to that PDSCH of that serving cell.

[0068] In procedure D3a, if the condition / threshold is not applicable (timeDurationforQCL [in FR1] is not reported), as in the example of Figure 1A, and regardless of the configuration of tci-PresentInDCI and tci-PresentDCI-1-2 in RRC connected mode, for a UE provided with dl-OrJointTCI-StateList-r17, if a PDSCH of a serving cell is scheduled by a CORESET that does not follow the indicated TCI state, the indicated TCI state may be applied to that PDSCH of that serving cell.

[0069] In procedure D3a, as in Figure 1B, if the condition / threshold is applicable (if timeDurationforQCL [in FR2] is reported), and regardless of the configuration of tci-PresentInDCI and tci-PresentDCI-1-2 in RRC connected mode, for a UE provided with dl-OrJointTCI-StateList-r17, if the PDSCH of a serving cell is scheduled by a CORESET that does not comply with the indicated TCI state and the time offset between reception of a DL DCI and the corresponding PDSCH is greater than or equal to the threshold timeDurationforQCL, the indicated TCI state may be applied to that PDSCH of that serving cell.

[0070] <Issues> In the first embodiment, the UE always uses the indicated TCI state in inter-cell beam management (ICBM, L1 / L2 inter-cell mobility) in FR1. If the indicated TCI state is associated with a non-serving cell PCI, the UE may receive a common signal from a non-serving cell (neighbor cell / candidate cell), which may make it technically impossible to deploy ICBM in FR1.

[0071] The common signal may include a channel carrying at least one of paging, short messages, and SIBs, a channel for scheduling the channel, a cell-common channel (PDCCH / PDSCH), a PDCCH in a CORESET associated with a CSS, or a QCL source RS for those channels. If the indicated TCI state is associated with a non-serving cell PCI, the common signal may not follow the indicated TCI state (it may follow the [configured] TCI state associated with the serving cell).

[0072] In the ICBM in FR1, if the indicated TCI state is associated with a non-serving cell PCI, the UE preferably uses a TCI state other than the indicated one for receiving a PDSCH scheduled by a PDCCH associated with a CSS. In FR2, if the indicated TCI state is associated with a non-serving cell PCI, the UE receives the PDSCH using the QCL assumption of the CORESET with the lowest ID (step D2-2 above). However, since timeDurationForQCL is not reported in FR1, the behavior of FR2 does not apply to FR1.

[0073] <Embodiment 2> The UE / BS may, within FR1, assume QCL for a PDSCH scheduled by a PDCCH in a CORESET that does not follow a unified TCI state depending on whether the indicated TCI state is associated with the serving cell PCI.

[0074] If the indicated TCI state is associated with the serving cell PCI, the PDSCH reception may follow the indicated TCI state; otherwise, the PDSCH reception may follow the QCL assumption / TCI state associated with the serving cell PCI.

[0075] According to the second embodiment, the UE / BS can appropriately determine / assume the QCL assumption of the PDSCH scheduled by the PDCCH in the CORESET that does not follow the unified TCI state within the FR1.

[0076] <<Embodiment 2-1>> If the indicated TCI state is associated with the serving cell PCI, PDSCH reception may follow the indicated TCI state; otherwise, PDSCH reception may follow the QCL assumptions of the CORESET with the lowest ID.

[0077] <<<Specific examples>>> Step D3 may be changed to the following steps D3b1x.

[0078] ◆ Procedure D3b11: [In FR1] In RRC connected mode, regardless of the configuration of tci-PresentInDCI and tci-PresentDCI-1-2, if the UE is provided with dl-OrJointTCI-StateList-r17 and the PDSCH of the serving cell is scheduled by a CORESET that does not comply with the indicated TCI state and none of the configured TCI states for the serving cell of the scheduled PDSCH contains qcl-Type set to 'typeD' [and timeDurationForQCL is not reported], the UE procedure may be based on at least one of the following procedures D3b11-x. - Step D3b11-1: If the indicated TCI state is associated with the PCI of the serving cell, the indicated TCI state is applied to PDSCH reception. -◆Step D3b11-2: If the indicated TCI state is associated with a PCI different from that of the serving cell, the UE may assume that one or more PDSCH DM-RS antenna ports of the serving cell are QCL'd with one or more RSs for one or more QCL parameters used in the PDCCH QCL indication of a CORESET that has the lowest controlResourceSetId and is associated with a monitored search space set in the most recent slot in which one or more CORESETs in the serving cell's active BWP are monitored by the UE.

[0079] ◆ Step D3b12: [In FR1] Regardless of the configuration of tci-PresentInDCI and tci-PresentDCI-1-2 in RRC connected mode, for a UE provided with dl-OrJointTCI-StateList-r17, if a PDSCH of a serving cell is scheduled by a CORESET that does not comply with the indicated TCI state, and at least one configured TCI state for the serving cell of the scheduled PDSCH includes qcl-Type set to 'typeD', and [if applicable] the time offset between reception of a DL DCI and the corresponding PDSCH is greater than or equal to the threshold timeDurationforQCL [or timeDurationForQCL is not reported], the indicated TCI state applies to that PDSCH of that serving cell.

[0080] <<Embodiment 2-2>> If the indicated TCI state is associated with the serving cell PCI, PDSCH reception may follow the indicated TCI state; otherwise, PDSCH reception may follow the same QCL assumptions as the scheduling CORESET.

[0081] <<<Specific examples>>> Step D3 may be changed to the following steps D3b2x:

[0082] ◆ Procedure D3b21: [In FR1] In RRC connected mode, regardless of the configuration of tci-PresentInDCI and tci-PresentDCI-1-2, if the UE is provided with dl-OrJointTCI-StateList-r17 and the PDSCH of the serving cell is scheduled by a CORESET that does not comply with the indicated TCI state and none of the configured TCI states for the serving cell of the scheduled PDSCH contains qcl-Type set to 'typeD' [and timeDurationForQCL is not reported], the UE procedure may be based on at least one of the following procedures D3b21-x. - Step D3b21-1: If the indicated TCI state is associated with the PCI of the serving cell, the indicated TCI state is applied to PDSCH reception. -◆Step D3b21-2: If the indicated TCI state is associated with a PCI different from that of the serving cell, the UE may assume that the DM-RS antenna ports of one or more PDSCHs of the serving cell are QCL'd with one or more RSs related to one or more QCL parameters used in the PDCCH QCL indication of that CORESET [that schedules the one or more PDSCHs].

[0083] ◆ Step D3b22: [In FR1] Regardless of the configuration of tci-PresentInDCI and tci-PresentDCI-1-2 in RRC connected mode, for a UE provided with dl-OrJointTCI-StateList-r17, if a PDSCH of a serving cell is scheduled by a CORESET that does not comply with the indicated TCI state, and at least one configured TCI state for the serving cell of the scheduled PDSCH includes qcl-Type set to 'typeD', and [if applicable] the time offset between reception of a DL DCI and the corresponding PDSCH is greater than or equal to the threshold timeDurationforQCL [or timeDurationForQCL is not reported], the indicated TCI state applies to that PDSCH of that serving cell.

[0084] <Embodiment 3> The UE / BS may assume that within FR1, the QCL assumption of a PDSCH scheduled by a PDCCH in a CORESET that does not follow the unified TCI state is the same as the QCL assumption of that CORESET.

[0085] According to the third embodiment, the UE / BS can appropriately determine / assume the QCL assumption of the PDSCH scheduled by the PDCCH in the CORESET that does not follow the unified TCI state within the FR1.

[0086] <<<Specific examples>>> Step D3 may be changed to the following steps D3c.

[0087] ◆Step D3c: [In FR1] For a UE provided with dl-OrJointTCI-StateList-r17 in RRC connected mode, regardless of the settings of tci-PresentInDCI and tci-PresentDCI-1-2, if [the PDSCH of the serving cell is scheduled by a CORESET that does not comply with the indicated TCI state, and] [if applicable] the time offset between the reception of the DL DCI and the corresponding PDSCH is greater than or equal to the threshold timeDurationforQCL [or timeDurationForQCL is not reported], the UE may assume that the DM-RS antenna ports of one or more PDSCHs of the serving cell are QCL'd with one or more RSs for one or more QCL parameters used in the PDCCH QCL indication of the CORESET [that schedules the one or more PDSCHs].

[0088] In step D3c, the QCL indication for that CORESET may be the TCI state configured for that CORESET. If the indicated TCI state is associated with a non-serving cell PCI, the CORESET associated with the CSS (including the PDCCH in that CORESET and the PDSCH scheduled by that PDCCH) may not follow the indicated TCI state (but may follow the TCI state associated with the serving cell).

[0089] <Variations> Among the above-mentioned multiple procedures for PDSCH antenna port quasi-co-location, when the scheduling offset is equal to or greater than timeDurationForQCL, there is a procedure that does not have the condition "if applicable." It is unclear whether this procedure applies to FR1.

[0090] It may be clarified that if timeDurationForQCL is not reported in FR1, the procedure applies.

[0091] <<<Specific examples>>> At least one of the above-described steps D1 and D3 may be changed to at least one of the following steps D1d and D3d, respectively.

[0092] ◆Step D1d: If the UE is not provided with dl-OrJointTCI-StateList-r17 (DL or joint TCI state list) and the PDSCH is scheduled by a DCI format with the presence of a TCI field and the TCI field in that DCI in the scheduling CC points to an activated TCI state in the scheduled CC or DL ​​BWP, the TCI-State according to the value of the 'Transmission Configuration Indication' (TCI) field in the detected PDCCH with DCI is used to determine the PDSCH antenna port QCL. If applicable, the UE assumes that the DM-RS port of the PDSCH of the serving cell is quasi-colocated with one or more RSs in the TCI state for one or more QCL type parameters given by the indicated TCI state if the time offset (scheduling offset) between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than the threshold timeDurationforQCL, where the threshold is based on the reported UE capabilities. For a single-slot PDSCH, the one or more indicated TCI states are based on one or more activated TCI states in the slot with the scheduled PDSCH. In the case of a multi-slot PDSCH, or if the UE is configured with the higher layer parameter pdsch-TimeDomainAllocationListForMultiPDSCH, the one or more indicated TCI states are based on one or more activated TCI states in the first slot with one or more scheduled PDSCHs, and the UE expects the one or more activated TCI states to be the same across multiple slots with one or more scheduled PDSCHs.If a UE is configured with a CORESET associated with a search space set for cross-carrier scheduling and the UE does not configure enableDefaultBeamForCCS, the UE shall expect tci-PresentInDCI to be set to 'enabled' or tci-PresentDCI-1-2 to be set for that CORESET, and if one or more TCI states configured for a serving cell scheduled by that search space set include qcl-Type set to 'typeD', the UE shall expect the time offset between the reception of a PDCCH detected within the search space set and the corresponding PDSCH to be greater than or equal to the threshold timeDurationforQCL, if applicable.

[0093] ◆Step D3d: Regardless of the settings of tci-PresentInDCI and tci-PresentDCI-1-2 in RRC connected mode, for a UE provided with dl-OrJointTCI-StateList-r17, if the PDSCH of the serving cell is scheduled by a CORESET that does not comply with the indicated TCI state and if the condition / threshold [that the time offset between the reception of DL DCI and the corresponding PDSCH is greater than or equal to the threshold timeDurationforQCL] is applicable, then if the time offset between the reception of DL DCI and the corresponding PDSCH is greater than or equal to the threshold timeDurationforQCL, the indicated TCI state is applied to that PDSCH of that serving cell.

[0094] In procedure D1d, if the condition / threshold is not applicable (if timeDurationforQCL is not reported [within FR1]), the UE may assume that the DM-RS ports of the serving cell's PDSCH are quasi co-located (QCLed) with one or more RSs within the TCI state regarding one or more QCL type parameters given by the indicated TCI state.

[0095] In procedure D3d, if the condition / threshold is not applicable (if timeDurationforQCL is not reported [within FR1]), in the case of a UE provided with dl-OrJointTCI-StateList-r17 in RRC connected mode regardless of the settings of tci-PresentInDCI and tci-PresentDCI-1-2, if the serving cell's PDSCH is scheduled by a CORESET that does not follow the indicated TCI state, the indicated TCI state may be applied to that PDSCH of that serving cell.

[0096] <Supplement> The above multiple embodiments / options / selections / variations may be combined as one embodiment / option / selections / variation.

[0097] <<Notification of Information to UE / BS>> Any notification of information from the [Network (NW) (e.g., Base Station (BS)) / NW node] to the UE / BS in the above embodiments (or in other words, reception of any information from the BS / NW node by the UE / BS) may be performed using physical layer signaling (e.g., DCI), upper layer signaling (e.g., RRC signaling, MAC CE, NAS signaling, LPP message, NRPPa message), specific signals / channels (e.g., PDCCH, PDSCH, reference signal), or combinations thereof.

[0098] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not defined in existing standards.

[0099] When the notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble the Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0100] In addition, notification of any information to the UE / BS in the above-described embodiments may be performed periodically, semi-persistently, or aperiodically. Notification of semi-persistent or aperiodically may be triggered by an instruction from the UE / BS / NW.

[0101] In the above-described embodiment, the information from the NW may be set / instructed by any one of the following methods or a combination thereof: Common to multiple UEs or individual to each UE (per UE). -Common to multiple BSs, or individual BSs (per BS). Common to multiple frequencies (e.g., one or a combination of cells, bands, band combinations, Bandwidth Parts (BWPs), component carriers, etc.) (e.g., cell-common), or frequency-specific (per frequency, e.g., per cell).

[0102] In the above embodiment, the UE may receive information (QCL information) of at least one of the following several QCL rules / QCL types from the NW: ◆QCL Type A (Doppler shift, Doppler spread, mean delay and delay spread). ◆QCL type B (Doppler shift and Doppler spread). ◆QCL Type C (Doppler shift and average delay). ◆QCL Type D (Spatial reception parameters).

[0103] In the above embodiments, the QCL source RS for each QCL type may be at least one of the following several RSs. ◆SSB. ◆CSI-RS with / without repetition. ◆TRS. ◆DMRS of PDCCH / PDSCH.

[0104] In the above embodiments, the information from the NW may be set / instructed by the following methods. ◆Common to multiple UEs or UE-specific. ◆Cell-specific or common to multiple cells. [[ID=​​​​​​​​​​​​​​​​ In addition, any information notification from the UE / BS in the above-mentioned embodiments may be performed periodically, semi-persistently, or aperiodically. Notification of semi-persistent or aperiodic information may be triggered by an instruction from the UE / BS / NW.

[0109] <<Application of each embodiment>> In a UE / BS, a particular (e.g., one or more, or part of) processing / operation / control / assumption / information of at least one of the above-described embodiments may be applied (used) when one or more of the following conditions are met: · Upper layer parameters indicating the above specific processing / operation / control / assumment / information are set in the UE / BS. The specific processing / action / control / assumption / information is determined in the UE / BS based on the relevant higher layer parameters. The above specific processing / action / control / assumption / information is specified / activated / triggered for the UE / BS by the MAC CE / DCI / UCI / resource / channel / RS. The UE / BS reports or supports specific capabilities (e.g., UE capabilities) that indicate (or relate to) the specific processing / action / control / assumptions / information. The application of the above specific processing / operation / control / assumption / information is determined in the UE / BS based on specific conditions.

[0110] The specified capabilities may indicate at least one of the following: ◆Supporting the above specific processing / action / control / assumptions / information. ◆Support the setting of dl-OrJointTCI-StateList-r17 for the serving cell [PDSCH setting].

[0111] In the present disclosure, "supporting" and "whether to support" may be read interchangeably.

[0112] Furthermore, the above-mentioned specific capabilities may be capabilities that are applied across all frequencies (commonly regardless of frequency), capabilities for each frequency (e.g., one or a combination of a cell, band, band combination, BWP, component carrier, etc.), capabilities for each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), capabilities for each subcarrier spacing (SubCarrier Spacing (SCS)), or capabilities for each Feature Set (FS) or Feature Set Per Component-carrier (FSPC).

[0113] Furthermore, the above-mentioned specific capabilities may be capabilities that are applied across all duplexing methods (commonly regardless of the duplexing method), or may be capabilities for each duplexing method (for example, Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

[0114] If the above conditions are not met, the UE / BS may follow the behavior specified in existing 3GPP releases.

[0115] (Addendum) The following inventions are added regarding one embodiment of the present disclosure. <Appendix 1> a receiver for receiving a configuration indicating a unified TCI state list; a control unit that applies a TCI state indicated in the unified TCI state list to reception of the PDSCH when a physical downlink shared channel (PDSCH) of a serving cell is scheduled by a physical downlink control channel (PDCCH) in a control resource set that does not comply with a unified TCI state and when a condition that a time offset between the PDCCH and the PDSCH is greater than or equal to a threshold cannot be applied. <Appendix 2> 2. The terminal according to claim 1, wherein, when the PDSCH is scheduled by a PDCCH in a control resource set that does not comply with a unified TCI state, and a TCI state related to spatial reception parameters is not configured for the serving cell, and a condition that a time offset between the PDCCH and the PDSCH is equal to or greater than a threshold cannot be applied, and the indicated TCI state is associated with a physical cell ID (PCI) of the serving cell, the control unit applies the indicated TCI state to reception of the PDSCH. <Appendix 3> 3. The terminal according to claim 1, wherein, when the PDSCH is scheduled by a PDCCH in a control resource set that does not comply with a unified TCI state, and a TCI state related to spatial reception parameters is not configured for the serving cell, and a condition that a time offset between the PDCCH and the PDSCH is equal to or greater than a threshold cannot be applied, and the indicated TCI state is associated with a PCI other than that of the serving cell, the controller applies a quasi co-location (QCL) assumption of the control resource set including the PDCCH or a control resource set with a lowest ID to reception of the PDSCH. <Appendix 4> The terminal according to any one of Supplementary Note 1 to Supplementary Note 3, wherein if the PDSCH is scheduled by a PDCCH in a control resource set that does not comply with a unified TCI state and the condition that a time offset between the PDCCH and the PDSCH is greater than or equal to a threshold cannot be applied, the control unit applies a QCL assumption of the control resource set to receiving the PDSCH. <Appendix A> a transmitter for transmitting a configuration indicating a unified TCI state list; a control unit that applies a TCI state indicated in the unified TCI state list to transmission of the PDSCH when the physical downlink shared channel (PDSCH) of a serving cell is scheduled by a physical downlink control channel (PDCCH) in a control resource set that does not comply with a unified TCI state and the condition that the time offset between the PDCCH and the PDSCH is equal to or greater than a threshold cannot be applied.

[0116] <Supplementary information> The terminal in Supplementary Notes 1 to 4 may be terminal 20. The receiver / transmitter in Supplementary Notes 1 to 4 may be transceiver 220. The controller in Supplementary Notes 1 to 4 may be controller 210. The base station in Supplementary Notes A may be base station 10. The receiver / transmitter in Supplementary Notes A may be transceiver 120. The controller in Supplementary Notes A may be controller 110.

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

[0118] 2 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment of the present disclosure. The wireless communication system 1 (which may be simply referred to as system 1) may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), or the like, which are specified by the Third Generation Partnership Project (3GPP).

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

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

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

[0122] 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 arranged within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A terminal 20 may be located within at least one of the cells. The arrangement, number, shape, size, etc. of each cell and terminal 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.

[0123] The wireless communication system 1 may utilize Multi Input Multi Output (MIMO). For example, one cell may be formed by one antenna / base station 10, or may be formed by multiple antennas / base stations 10. One [virtual] cell (which may be called, for example, a super cell) may be composed of multiple [virtual] cells (which may be called, for example, sub-cells). A super cell may correspond to a cell whose physical range is fixed, and a sub-cell may correspond to a cell whose physical range varies semi-statically / dynamically. In this case, the wireless communication system 1 may be called a cell-free system.

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

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

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

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

[0128] 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, 5GC), a Next Generation Core (NGC), and the like.

[0129] The core network 30 may include network functions (Network Functions (NFs)) such as a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Note that a single network node (which may simply be referred to as a node) may provide multiple functions. Furthermore, communication with an external network (e.g., the Internet) may be performed via the DN.

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

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

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

[0133] In the wireless communication system 1, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each 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.

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

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

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

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

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

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

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

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

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

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

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

[0145] (base station) 3 is a diagram illustrating an example of the configuration of a base station according to an embodiment of the present disclosure. 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0162] The base station 10 may be separated into three elements: a radio unit (RU), a distributed unit (DU), and a central unit (CU). For example, the RU may perform RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level functions of the physical layer (precoding, IFFT, FFT, etc.). The DU may perform higher-level functions of the physical layer (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may perform PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.

[0163] In the present disclosure, the base station 10 may include a single device that implements all of the functions of the RU, DU, and CU, or may include multiple devices that each implement some of the functions of the RU, DU, and CU and are connected to each other. In the present disclosure, the base station 10 may be interchangeably read as RU / DU / CU.

[0164] Furthermore, in the present disclosure, a network device (for example, an LMF node) having the functionality of any of the above-described NFs may be a device having the configuration (for example, the control unit 110 and the transceiver unit 120) of the base station 10. In other words, by replacing the base station with the network device, the configuration of the network device according to an embodiment of the present disclosure may be covered.

[0165] (Terminal) 4 is a diagram illustrating an example of the configuration of a terminal according to an embodiment of the present disclosure. The terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the terminal may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0181] The measurement unit 223 may derive channel measurements for CSI calculation based on the channel measurement resources. The channel measurement resources may be, for example, non-zero power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on the interference measurement resources. The interference measurement resources may be at least one of an NZP CSI-RS resource for interference measurement, a CSI-Interference Measurement (IM) resource, etc. Note that CSI-IM may be referred to as CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS. Note that in the present disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be interchangeably read as interchangeable.

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

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

[0184] For example, a base station, a terminal, a network node, 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. 5 is a diagram illustrating an example of the hardware configuration of a base station and a terminal according to an embodiment of the present disclosure. The above-described base station 10 and 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.

[0185] In the present disclosure, any two terms selected from a set of terms such as apparatus, circuit, device, section, unit, module, chip, means, etc. may be read as interchangeable. The hardware configurations of the base station 10 and the 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.

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

[0187] 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. Although only one processor 1001 is shown in the figure, there may be multiple processors.

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

[0189] The various processes described above may be performed by one processor 1001, or may be performed by two or more processors 1001 simultaneously, sequentially, or using other techniques. The processor 1001 may be implemented by one or more chips. The program may be transmitted from a network via a telecommunications line, or may be provided to the computer device via, for example, the communication device 1004.

[0190] The present disclosure also provides a computer program product including a computer program, which may implement the steps of the methods described in the above embodiments when the computer program is executed by a computer (e.g., the processor 1001).

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

[0192] Storage 1003 is a non-transitory computer-readable recording medium, and may be, for example, a flexible disk, a floppy disk, an optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a magneto-optical disk, a removable disk, a hard disk drive, a smart card, a flash memory (e.g., a card, stick, key drive), a magnetic stripe, or the like, or a combination of at least two of these. Storage 1003 may also be referred to as a secondary storage device.

[0193] The above-mentioned recording medium may be, for example, the memory 1002, the storage 1003, or a database including both the memory 1002 and the storage 1003, a server, or other suitable medium.

[0194] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via a wired network, a wireless network, or both a wired network and a wireless network, and is also referred to as a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., or a combination of at least two of these. 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.

[0195] The input device 1005 is an input device that accepts input from the outside (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc., or a combination of at least two of these). The output device 1006 is an output device that performs output to the outside (for example, a display, a speaker, a Light Emitting Diode (LED) lamp, etc., or a combination of at least two of these). Note that the input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

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

[0197] Furthermore, base station 10 and 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), a field programmable gate array (FPGA), a graphics processing unit (GPU), a neural processing unit (NPU), or a combination of at least two of these, and some or all of the functional blocks may be realized using such hardware. For example, processor 1001 may be implemented using at least one of these hardware elements.

[0198] In this disclosure, the term "processor" may encompass a single processor or a group of multiple processors, including, for example, a single-core processor, a multi-core processor, multiple processors in a single device, multiple processors in wired or wireless communication with each other, etc. Similarly, the term "(non-transitory) computer-readable storage medium" may encompass a single storage medium or a group of multiple storage media, including multiple storage media in wired or wireless communication with each other.

[0199] Devices such as processors and storage media in the present disclosure may be distributed locally or remotely, and may perform the processing of the devices by operating cooperatively or independently using a bus, network, the Internet, the cloud, etc.

[0200] Note that the devices included in the core network 30 (for example, network nodes that provide NFs) may also be realized by the above-described functional block / hardware configuration.

[0201] (Variation) Each aspect / embodiment described in the present disclosure may be a mobile communication system other than Long Term Evolution (LTE), LTE-Advanced (LTE-A), International Mobile Telecommunications-Advanced (IMT-Advanced), 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G-Advanced (5G-A), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or a decimal number)), Future Radio Access (FRA), New Radio (NR), New radio access (NX), Future generation radio access (FX), Open Radio Access Network (Open RAN (O-RAN)), Wideband Code Division Multiple Access (W-CDMA (registered trademark)), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.11x (where x is any character string such as b, a, g, n, ac, ax, be, or bn, and when x = n, it is called Wi-Fi 4, when x = ac, it is called Wi-Fi 5, when x = ax, it is called Wi-Fi 6 or Wi-Fi 6E, when x = be, it is called Wi-Fi 7, and when x = bn, it is called Wi-Fi 8.Note that the present disclosure may be applied to systems based on technologies such as Wi-Fi (a registered trademark), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), network virtualization technologies (e.g., Network Function Virtualization (NFV), Service Function Chaining (SFC), Software Defined Networking (SDN)), or Low Power Wide Area (LPWA). Furthermore, each aspect / embodiment described in the present disclosure may be applied to a system based on a combination of at least two of these technologies. Here, "based on" naturally refers not only to a system that uses the technology in question, but also to a system that uses an extension or modification of the technology.

[0202] In the present disclosure, any two terms selected from a set of terms such as "Base Station (BS)", "Radio Base Station", "Fixed Station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "Access Point (AP)", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "Radio Unit (RU)", "Remote Unit (RU)", "Control Unit (CU)", "Distributed Unit (DU)", "Remote Radio Head (RRH)", "node", "gateway", "terrestrial base station", "stratospheric base station", "unmanned aerial vehicle", "High Altitude Platform Station (HAPS)", "airborne platform", "panel", "cell", "Radio Access Network (RAN)", "network", etc. may be used interchangeably. Each cell accommodated by a base station may be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, a serving cell, a super cell, etc. In the present disclosure, any two terms selected from a set of terms such as "cell," "sector," "cell group," "carrier," "component carrier," "cluster," "bandwidth part (BWP)," and "carrier bandwidth" may be used interchangeably.

[0203] In the present disclosure, any two terms selected from the set of terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "Device", "Module", "Terminal", etc. may be used interchangeably.

[0204] A terminal may 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, router (e.g., home router, mobile router, etc.), Telematics Control Unit (TCU), or some other suitable terminology.

[0205] The base station and the terminal may each be composed of one or more devices. The devices constituting at least a part of the base station and the terminal may be called a transmitting device, a receiving device, a [wireless] communication device, etc. In addition, the devices constituting at least a portion of each of the base stations and terminals may be objects themselves, such as 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, unmanned aerial vehicles, stratospheric base stations (e.g., High Altitude Platform Stations (HAPS)), artificial satellites (e.g., Low Earth Orbit (LEO) satellites, Middle Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites), drones (registered trademark), multicopters, quadcopters, balloons, Internet of Things (IoT) equipment (e.g., smart meters, sensors), etc., or may include, but are not limited to, objects or devices mounted on such objects. Furthermore, the object may be a moving object (hereinafter referred to as a "moving object"; this does not exclude the case where the moving object is stationary and not moving), or may be a fixedly positioned object (hereinafter referred to as a "non-moving object").

[0206] Furthermore, a base station in the present disclosure may be read as a 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 terminal is replaced with communication between multiple terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)) or communication in a non-terrestrial network (Non-Terrestrial Network (NTN)). In this case, the 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 communication between terminals (for example, "sidelink") or terms corresponding to NTN (for example, feeder link, service link). For example, terms such as uplink channel and downlink channel may be read as sidelink channel.

[0207] The present disclosure is also applicable to cases where at least some of the devices constituting the base station and the terminal operate outside the earth (for example, in the atmosphere or outer space).

[0208] Similarly, the term "terminal" in the present disclosure may be read as "base station." In this case, the base station 10 may be configured to have the functions of the terminal 20 described above.

[0209] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node or by some of its upper nodes (e.g., CU, RU, DU, etc.) in some cases. It is clear that various operations performed for communication with a terminal in a RAN or core network may be performed by at least some of the base station and other network nodes other than the base station. The other network node may be one node or a combination of multiple nodes. The network node is, for example, a node provided in various core networks such as an Evolved Packet Core (EPC) or a 5G Core Network (5GCN, 5GC), and provides one or more network functions (Network Functions (NFs)), but is not limited to these.

[0210] Furthermore, in the present disclosure, the operation of "a terminal receives information from a base station" accompanies the operation of "the base station transmits the information to the terminal," "the base station generates the information," or both. Similarly, the operation of "a terminal transmits information to a base station" accompanies the operation of "the base station receives the information from the terminal." Furthermore, operations such as "a terminal is configured to ..." or "configure UE to ..." may include the operation of "a base station transmits configuration information regarding the configuration of the terminal" or "a terminal configures a predetermined operation based on the configuration information."

[0211] 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 of at least two of them.

[0212] The physical layer signaling may be referred to as Layer 1 (L1) control information. The MAC signaling may be referred to as, for example, a MAC Control Element (CE) or a MAC Protocol Data Unit (PDU). The RRC signaling may be referred to as an RRC message or an information element (IE) in the RRC message. The RRC signaling may be, for example, a message used for controlling an RRC connection (e.g., setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, a measurement report, notification of terminal capabilities, or an information element in the message.

[0213] Furthermore, notification of information may be either explicit or implicit. Note that an explicit notification of certain information means notification of the certain information itself, and an implicit notification of certain information may mean notification of information other than the certain information, or the certain information being deemed to have been notified when a certain condition is met.

[0214] Furthermore, notification of information may include not only notification between the same layers of different devices (for example, between a lower layer or an upper layer of the base station 10 and the terminal 20) but also notification between different layers in the same or different devices (for example, between a lower layer and an upper layer in the base station 10 or the terminal 20). Furthermore, notification of information from one device to another device may be performed via one or more devices.

[0215] With respect to any information (e.g., variables, constants, parameters, settings) described in the present disclosure, even if not specifically stated in the above embodiments, any first device (e.g., terminal / base station) may notify any second device (e.g., base station / terminal) of information indicating / identifying (or relating to) the value of the any information.

[0216] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed as long as it is consistent. For example, the methods described in this disclosure present various step elements using an exemplary order and are not limited to the particular order presented. Furthermore, at least one step may be omitted in the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure.

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

[0218] In the present disclosure, a radio resource may be defined by a combination of resource units in one or more domains, such as the time domain, the frequency domain, the spatial domain, the code domain, and the power domain.

[0219] For example, a resource in the time domain (which may be referred to as a time resource) may be defined by one or more time units. The one or more time units may include, but are not limited to, a radio frame, a subframe, a slot, a symbol, a transmission time interval (TTI), or a combination of at least two of these. Furthermore, the time unit may be a fixed-length time unit that is independent of numerology, a variable-length time unit that is dependent on numerology, or both.

[0220] Examples of fixed-length time units include, but are not limited to, subframes each consisting of one or more slots and radio frames each including multiple subframes. Examples of variable-length time units include, but are not limited to, symbols and slots each including a fixed number of symbols. A certain time unit may be divided into time units shorter than the certain time unit. Examples of such shorter time units include, but are not limited to, minislots each consisting of fewer symbols than the number of symbols that make up a slot. The above-described time units may include time units used as units for scheduling, link adaptation, and the like. Any time unit in the present disclosure may be interchangeable with another time unit.

[0221] Numerology is a parameter that defines the physical layer structure, and may be a parameter based on at least one of the subcarrier spacing (SCS), the symbol length, the cyclic prefix length, and the sampling time, for example.

[0222] A resource in the frequency domain (which may also be referred to as a frequency resource) may be defined by, for example, one or more frequency units. The one or more frequency units may include, for example, a subcarrier, a resource block (RB), a bandwidth part (BWP), a carrier bandwidth, or a combination of at least two of these, but the name of the frequency unit is not limited to these. Furthermore, the number of subcarriers included in a certain frequency unit may be a fixed number regardless of numerology, or may be a variable number that changes depending on numerology.

[0223] For example, an RB is composed of a predetermined number of consecutive subcarriers in the frequency domain, and the number of subcarriers included in the RB may be the same regardless of numerology, for example, 12, but is not limited to this. Also, a BWP may be composed of, for example, one or more consecutive RBs within a certain carrier bandwidth, but is not limited to this. One or more BWPs may be configured within one carrier for terminal 20, and at least one of the BWPs may be activated. Also, any frequency unit in the present disclosure may be interpreted as another frequency unit.

[0224] Furthermore, resources in both the time domain and the frequency domain may be defined by one or more time / frequency units each consisting of a time unit and a frequency unit, such as, but not limited to, a resource element (RE) consisting of one symbol and one subcarrier, a resource element group (REG) consisting of a predetermined number of REs, or a control resource set (CORESET) consisting of a predetermined number of symbols and a predetermined number of RBs.

[0225] The resources in the spatial domain (which may also be referred to as spatial resources) may be defined, for example, by one or more spatial units, including, but not limited to, beams, layers of Multi-Input Multi-Output (MIMO), antenna ports, etc., or a combination of at least two of them.

[0226] The resource in the code domain (which may also be referred to as a code resource) may be defined by, for example, one or more code units, including, but not limited to, a Cyclic Shift (CS), an Orthogonal Cover Code (OCC), or a combination thereof.

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

[0228] In the present disclosure, terms such as "decide," "determine," "judge," "select," "specify," "compute," "calculate," "process," "derive," "look up / search / inquiry," "confirm," "assume," "expect," and "consider" may be read interchangeably. Also, in the present disclosure, performing a certain process (e.g., sending, receiving) may be read interchangeably as deciding to perform that process. Also, in the present disclosure, "not expected to do..." may be read interchangeably as "assumed not to do...."

[0229] In the present disclosure, "expect" may be interchangeably read as "be expected." For example, "expect(s) ..." ("..." may be expressed, for example, as a that clause, a to-infinitive, etc.) may be interchangeably read as "be expected ...," "do ... (if the above "..." is a to-infinitive, a verb with "to")," etc. "does not expect ..." may be interchangeably read as "be not expected ...," "does not ... (if the above "..." is a to-infinitive, a verb with "to")," etc. Furthermore, "An apparatus A is not expected ..." may be interchangeably read as "an apparatus B other than apparatus A does not expect ... from apparatus A" (for example, if apparatus A is a UE, apparatus B may be a base station).

[0230] 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 the prefix "i-th" (i is any integer) (for example, "highest" may be interchangeable as "i-th highest").

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

[0232] In the present disclosure, terms such as "when A, B," "if A, (then) B," "B upon A," "B in response to A," "B based on A," "B during / while A," "B before A," "B at (the same time as) / on A," "B after A," "B since A," and "B until A" may be interchangeable. Note that A, B, and the like herein may be replaced with appropriate expressions, such as nouns, gerunds, and regular sentences, depending on the context. Note that the time difference between A and B may be nearly zero (immediately after or immediately before). A time offset may be applied to the time at which A occurs. For example, "A" may be interchangeable with "before / after the time offset at which A occurs." The time offset (eg, one or more symbols / slots) may be predefined or may be specified by the UE based on signaled information.

[0233] In the present disclosure, timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc. may be read interchangeably.

[0234] 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 relation information," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "port," "layer," "number of layers," "rank," "resource," "resource set," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," "UE panel," "transmitting entity," "receiving entity," etc. may be used interchangeably.

[0235] In the present disclosure, an antenna port may be interchangeably read as an antenna port for any signal / channel (e.g., a Demodulation Reference Signal (DMRS) port). In the present disclosure, a resource may be interchangeably read as a resource for any signal / channel (e.g., a reference signal resource). Furthermore, the spatial domain filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0236] In the present disclosure, beam, sounding reference signal (SRS) resource indicator (SRS Resource Indicator (SRI)), control resource set (CONTROLLER RESOLUTION SET (CORESET)), CORESET pool, uplink shared channel (Physical Downlink Shared Channel (PDSCH)), uplink shared channel (Physical Uplink Shared Channel (PUSCH)), codeword (CW), transport block (TB), reference signal (RS), etc. may be interpreted as interchangeable.

[0237] In the present disclosure, the terms TCI state, TCI, downlink TCI state (Downlink (DL) TCI state), uplink TCI state (Uplink (UL) TCI state), unified TCI state, common TCI state, joint TCI state, etc. may be read interchangeably.

[0238] Furthermore, in this disclosure, terms such as "QCL," "QCL assumptions," "QCL relationships," "QCL type information," "QCL properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

[0239] In this disclosure, terms such as index, identifier (ID), identity (ID), indicator, indication, resource ID, etc. may be interchangeable. In this disclosure, terms such as sequence, list, set, group, cluster, subset, etc. may be interchangeable.

[0240] In the present disclosure, a group may include, for example, at least one of a spatial relationship group, a Code Division Multiplexing (CDM) group, an RS group, a CORESET group, a Physical Uplink Control Channel (PUCCH) group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, a panel group, and the like.

[0241] Information in this disclosure (e.g., variables, constants, parameters, settings) may be interchangeably read as the ID of the information. For example, TCI state and TCI state ID may be interchangeably read as the ID of the information. Also, information in this disclosure may be interchangeably read as "a set of the information," "one or more pieces of the information," etc.

[0242] Any signal / channel (e.g., PUCCH) in the present disclosure may be interchangeably read as another signal / channel (e.g., PUSCH, PDSCH, any RS). A signal / channel may be interchangeably read as a signal / channel for the same direction (e.g., UL if the certain signal / channel is in the UL direction, and DL if in the DL direction), or as a signal / channel for another direction (e.g., DL if the certain signal / channel is in the UL direction, and UL if in the DL direction). Also, in the present disclosure, descriptions related to DL communication and descriptions related to UL communication may be interchangeably read. In this case, DL (UL) operation may be interchangeably read as the corresponding UL (DL) operation. For example, reception of a PDSCH in a terminal may be interchangeably read as transmission of a PUSCH in the terminal.

[0243] In the present disclosure, terms such as "X's number," "X number," "the number of X(s)," and "a number of X(s)" may be interchangeable. Note that X here may be replaced with an appropriate expression such as a noun, a gerund, or an ordinary sentence, depending on the context. In the present disclosure, "number" may be interchangeable with terms such as maximum number, minimum number, average number, and total number. In addition, in the present disclosure, terms such as "value," "index," "number," and "quantity" may be interchangeable with each other.

[0244] Values / ranges in this disclosure may be interpreted as approximations, as if the words "about" or "approximately" were preceding the value / range. In this disclosure, "A and B are the same" (A and B are any words) may mean "A and B are identical," "A and B are almost the same," "A and B are partly the same (or partially overlapped)," "There is an error within a certain range between A and B," etc. (i.e., these words may be read interchangeably). Furthermore, in the present disclosure, A and B being the same may mean that at least part of A and at least part of B are the same (or overlapped).

[0245] In this disclosure, the terms "one embodiment," "some embodiments," "another embodiment," etc. may be used interchangeably. The appearances of phrases such as "one embodiment," "some embodiments," "another embodiment," etc. in this disclosure do not necessarily all refer to the same embodiment, nor are they necessarily meant to be mutually exclusive.

[0246] In the present disclosure, expressions such as "at least one of A and B," "at least one of A or B," "A and / or B," and "A / B" may be read interchangeably, and may be understood to include "only A," "only B," or "both A and B." Furthermore, in this disclosure, expressions such as "at least one of A, B, and C," "at least one of A, B, or C," "A, B and / or C," and "A / B / C" may be interpreted interchangeably and may be understood to include "only A," "only B," "only C," "A and B," "B and C," "C and A," or "all of A, B, and C." Note that similar interpretations / interpretations may be applied to any expression in this disclosure such as "at least X of ..." (where the number of elements in "..." and X are each any number).

[0247] In the present disclosure, expressions such as "A, [and] B, and the like" / "such as A [and] B"), "A, [or] B, or the like" / "such as A [or] B"), "A, B, etc." / "A, B, and so on" / "A, B, and so forth"," and "A, B, [and / or] the others" may be read interchangeably.

[0248] In the present disclosure, expressions representing one / single X (e.g., "a X," "one X," "a single X"), expressions representing one or more Xs (e.g., "one or more X(s)," "at least one of X(s)"), and expressions representing a plurality of Xs (e.g., "Xs," "more than one X(s)," "multiple X(s)," "a plurarity of X(s)") may be read interchangeably. Note that these expressions may also be read interchangeably with expressions that include specific wording (e.g., when X is an uncountable noun, "pieces of," "amount of," etc.). For example, "a plurality of pieces of spatial relation information" may be read interchangeably as "a plurality of spatial relation information."

[0249] The present disclosure has been described above, but it is for illustrative purposes only, and the present invention is not limited to the aspects / embodiments described in the present disclosure. The present disclosure can be implemented in modified and altered forms without departing from the spirit of the invention. The present disclosure and its modifications and alterations are included in the scope of the present invention and its equivalents.< / srs> < / pusch> < / pucch> < / pdsch> < / pdcch>

Claims

1. a receiver for receiving a configuration indicating a unified TCI status list; a control unit that applies an indicated TCI state in the unified TCI state list to reception of the PDSCH when a physical downlink shared channel (PDSCH) of a serving cell is scheduled by a physical downlink control channel (PDCCH) in a control resource set that does not follow a unified TCI state and when a condition that a time offset between the PDCCH and the PDSCH is greater than or equal to a threshold cannot be applied.

2. 2. The terminal of claim 1, wherein the PDSCH is scheduled by a PDCCH in a control resource set that does not comply with a unified TCI state, and a TCI state related to spatial reception parameters is not configured for the serving cell, and a condition that a time offset between the PDCCH and the PDSCH is equal to or greater than a threshold cannot be applied, and the indicated TCI state is associated with a physical cell ID (PCI) of the serving cell, the controller applies the indicated TCI state to reception of the PDSCH.

3. 2. The terminal of claim 1, wherein, when the PDSCH is scheduled by a PDCCH in a control resource set that does not comply with a unified TCI state, and a TCI state regarding spatial reception parameters is not configured for the serving cell, and a condition that a time offset between the PDCCH and the PDSCH is equal to or greater than a threshold cannot be applied, and the indicated TCI state is associated with a PCI other than that of the serving cell, the controller applies a quasi co-location (QCL) assumption of the control resource set including the PDCCH or a control resource set with a lowest ID to reception of the PDSCH.

4. 2. The terminal of claim 1, wherein, when the PDSCH is scheduled by a PDCCH in a control resource set that does not comply with a unified TCI state and a condition that a time offset between the PDCCH and the PDSCH is equal to or greater than a threshold cannot be applied, the controller applies a QCL assumption of the control resource set to reception of the PDSCH.

5. receiving a configuration indicating a unified TCI state list; and applying an indicated TCI state in the unified TCI state list to reception of a physical downlink shared channel (PDSCH) of a serving cell when the physical downlink control channel (PDCCH) in a control resource set does not comply with a unified TCI state and a condition that a time offset between the PDCCH and the PDSCH is equal to or greater than a threshold cannot be applied.

6. a transmitter for transmitting a configuration indicating a unified TCI status list; a controller that applies a TCI state indicated in the unified TCI state list to transmission of the PDSCH when the PDSCH of a serving cell is scheduled by a PDCCH in a control resource set that does not follow a unified TCI state and the time offset between the PDCCH and the PDSCH is greater than or equal to a threshold.

Images