Terminal, wireless communication method, and base station

By determining PDCCH monitoring occasions based on TCI states and optimizing TCI state application in a unified framework, the solution addresses communication quality and throughput issues in wireless systems, enhancing performance.

WO2026239900A1PCT designated stage Publication Date: 2026-11-19NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2026/016430
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-14
Filing Date
2026-04-24
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

The operation of unified transmission configuration indication (TCI) states in existing wireless communication systems has not been adequately considered, leading to potential deterioration in communication quality and throughput.

Method used

A terminal and base station implementation that determines PDCCH monitoring occasions based on a synchronization signal block referenced by a TCI state, utilizing a unified TCI framework to manage multiple channels and signals with common beam configurations, and employing MAC CE and DCI-based TCI state indications to optimize channel-specific TCI state application.

Benefits of technology

Improves communication quality and throughput by ensuring proper application of TCI states across various channels and signals, enhancing the unified TCI framework's efficiency and effectiveness.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2026016430_19112026_PF_FP_ABST
    Figure JP2026016430_19112026_PF_FP_ABST
Patent Text Reader

Abstract

A terminal according to one aspect of the present disclosure has: a reception unit that receives a configuration of a control resource set having an index 0 and receives an indication of at least one transmission configuration indication (TCI) state; and a control unit that, when the at least one TCI state above constitutes two TCI states and the configuration includes a first parameter for determining one TCI state from among the two TCI states, determines a monitoring occasion for at least one physical downlink control channel (PDCCH) candidate of a search space having an index 0 on the basis of a synchronization signal block referred to by the one TCI state.
Need to check novelty before this filing date? Find Prior Art

Description

Terminal, wireless communication method, and base station

[0001] This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems.

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was specified with the aim of achieving even higher data rates and lower latency (Non-Patent Literature 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was specified with the aim of further increasing the capacity and sophistication of LTE (Third Generation Partnership Project (3GPP®) Release (Rel.) 8, 9).

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

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

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

[0006] However, the operation of such TCI states has not been sufficiently considered. If TCI states are not applied properly, communication quality / throughput may deteriorate.

[0007] Therefore, one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that can improve communication performance / throughput.

[0008] A terminal according to one aspect of the present disclosure includes a receiving unit that receives a setting of a control resource set having index 0 and an instruction for one or more transmission configuration indication (TCI) states, and a control unit that, if the one or more TCI states are two TCI states and the setting includes a first parameter for determining one of the two TCI states, determines the monitoring occasion for one or more physical downlink control channel (PDCCH) candidates in a search space having index 0 based on a synchronization signal block referenced by the one TCI state.

[0009] According to one aspect of this disclosure, communication quality / throughput can be improved.

[0010] Figure 1 shows an example of determining the PDCCH monitoring occasion for SS#0. Figure 2 shows an example of determining the PDCCH monitoring occasion for SS#0 according to Embodiment 1. Figure 3 shows an example of the schematic configuration of a wireless communication system according to one embodiment of this disclosure. Figure 4 shows an example of the configuration of a base station according to one embodiment of this disclosure. Figure 5 shows an example of the configuration of a terminal according to one embodiment of this disclosure. Figure 6 shows an example of the hardware configuration of a base station and a terminal according to one embodiment of this disclosure.

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

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

[0013] The Unified TCI Framework supports the following modes 1 through 3: <<Mode 1>> MAC CE based TCI state indication <<Mode 2>> DCI based TCI state indication by DCI format 1_1 / 1_2 with DL assignment <<Mode 3>> DCI based TCI state indication by DCI format 1_1 / 1_2 without DL assignment

[0014] Furthermore, the DCI in Mode 2 / Mode 3 described above may also be called beam-indicating DCI.

[0015] In this disclosure, the terms DCI-indicated TCI state, indicated TCI state, indicated TCI state, indicated TCI-State, unified TCI state, TCI state conforming to a unified TCI state, TCI state applied to multiple types of channels / signals, joint TCI state for DL ​​and UL, DL TCI state, UL TCI state, Rel. 17 TCI state, common TCI state, single unified TCI state to be set, and single unified TCI state to be activated may be interpreted as one another.

[0016] In this disclosure, the terms TCI state set by RRC parameters, configured TCI state, configured TCI state, configured TCI-State, TCI state that does not conform to the unified TCI state, TCI state other than the unified TCI state, TCI state / spatial relationship set for a specific channel / signal, and individual TCI state may be interpreted interchangeably.

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

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

[0019] <<PDSCH>> A single TCI state applied to a PDSCH may be based on the following: ◆ For all UE-dedicated PDSCHs, the indicative TCI state is always applied. ◆ For non-UE-dedicated PDSCHs (PDSCHs scheduled by DCI in a CSS [set]), the indicative TCI state may be applied if followUnifiedTCIState is set [for the CORESET of the PDCCH that schedules the PDSCH]. Otherwise, the set TCI state for that PDSCH is applied to that PDSCH. If followUnifiedTCIState is not set for a PDSCH, whether a non-UE-dedicated PDSCH follows the indicative TCI state may be determined by whether followUnifiedTCIState is set for the CORESET used to schedule that PDSCH.

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

[0021] <<PUCCH>> A single TCI state applied to PUCCH may be based on the following: ◆The indicative TCI state is always applied to all dedicated PUCCH resources.

[0022] <<PUSCH>> A single TCI state applied to a PUSCH may be based on the following: ◆ For a dynamic / configured grant PUSCH, the instructive TCI state is always applied.

[0023] <<SRS>> A single TCI state applied to an SRS may be based on the following: ◆ For aperiodic (A)-SRS for beam management applications and for codebook (CB) / non-codebook (NCB) / antenna switching applications A / semi-persistent (SP) / periodic (P)-SRS, the indicative TCI state is applied if the SRS resource set is configured to follow a unified TCI state. For other SRSs, the configured TCI state within that SRS resource set is applied.

[0024] In this disclosure, the terms "indicator TCI state," "unified TCI state," "TCI state applied to a channel / signal configured to conform to a unified TCI state," "TCI state applied to UE individual PDSCH and CORESET / PDCCH associated with USS [set]," and "TCI state applied to PUCCH and PUSCH" may be interpreted interchangeably.

[0025] <Rel. 17 Procedure for TCI status (Antenna port pseudo-collocation)> PDSCH antenna port pseudo-collocation is based on the following procedure Ax.

[0026] ◆Procedure A6: If a PDSCH is scheduled in a DCI format in which no TCI field exists, and the threshold timeDurationforQCL is applicable, and the time offset (scheduling offset) between the reception of the DL DCI and the corresponding PDSCH of the serving cell is greater than or equal to the threshold timeDurationforQCL, the UE assumes that the TCI state or QCL assumption for that PDSCH is the same as any TCI state or QCL assumption applied to the CORESET used for PDCCH transmission in the serving cell's active BWP. Here, the threshold is based on the UE capability reported for PDSCH antenna port pseudo-collocation.

[0027] ◆Procedure A7: In RRC CONNECTED mode, regardless of the settings of tci-PresentInDCI and tci-PresentDCI-1-2, if the UE is provided with dl-OrJointTCI-StateList-r17, and the offset (time offset, scheduling offset) between the reception of 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 a qcl-Type set to 'typeD', then regardless of the setting of followUnifiedTCI-State, the UE procedure is based on the following procedure A7-x.

[0028] ―◆Procedure A7-1: If the specified TCI state is associated with the physical cell ID (PCI) of the serving cell, the specified TCI state is applied to the PDSCH iteration.

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

[0030] <Application of Indicator TCI in Rel. 18 (sDCI mTRP)> In sDCI multi-TRP (mTRP), the application of indicator TCI status may be based on the following:

[0031] <<PDCCH>> One or more TCI states applied to PDCCH may be based on the following: ◆ If followUnifiedTCIState is set for CORESET0, applyIndicatedTCIState={first TCI state, second TCI state, both} is set for each CORESET to indicate which indicated TCI state applies. Otherwise, the Rel. 15 specification is applied to that CORESET. That is, CORESET0 follows the TCI state activated by MAC CE, or is QCL'd with SSB. "Both" does not apply to CORESET0 with SearchSpace0 for type 0 / 0A / 2 CSS sets. ◆For CORESETs other than index 0 with USS / CSS type 3, applyIndicatedTCIState={first TCI state, second TCI state, both} is set for each CORESET to indicate which indicated TCI state should be applied. ◆For CORESETs other than index 0 with at least CSS other than CSS type 3, if it is configured to follow a unified TCI state, applyIndicatedTCIState={first TCI state, second TCI state, both} is set for each CORESET to indicate which indicated TCI state should be applied. Otherwise, the configured TCI state for that CORESET will be applied to that CORESET.

[0032] <<PDSCH>> For a PDSCH, one or two instruction TCI states are always applied. The one or more TCI states applied to a PDSCH may be based on the following: ◆ For a PDSCH scheduled / activated by DCI format 1_1 / 1_2, the 2-bit TCI selection field in the scheduling / activation DCI format 1_1 / 1_2 can indicate which instruction TCI state {first TCI state, second TCI state, or both} is applied. If the TCI selection field is not set, both instruction TCI states are applied. ◆ For a PDSCH scheduled / activated by DCI format 1_0, the RRC sets which instruction TCI state {first TCI state, second TCI state, or both} is applied. ◆ If PDSCH-CJT (CJT-PDSCH) or PDSCH-SFN (SFN-PDSCH) is set, only both instruction TCI states can be set.

[0033] <<CSI-RS>> One or more TCI states applied to a CSI-RS may be based on the following: ◆ For an A-CSI-RS for CSI acquisition or beam management, if followUnifiedTCIState is set [for the PDCCH CORESET that triggers that A-CSI-RS], applyIndicatedTCIState={first TCI state, second TCI state, both} is set for each CSI-RS resource set or each CSI-RS resource to indicate which indicated TCI state should be applied. For other CSI-RSs, the configured TCI state for that CSI-RS is applied.

[0034] <<TCI State Indication for PDSCH-CJT>> In sDCI mTRP, the TCI state indication for PDSCH-CJT may be based on the following. ◆ One or two indicated joint TCI states are applied to PDSCH-CJT (spanning up to four TRPs). Up to four TRPs share the same one or two TCI states (QCL source RS of TRS / CSI-RS). ◆ The following two schemes are supported. -◆ CJT Scheme A (cjtSchemeA): The PDSCH DM-RS ports are QCLed with multiple DL-RSs of both indicated TCI states for QCL Type A. -◆ CJT Scheme B (cjtSchemeB): The PDSCH DM-RS ports are QCLed with multiple DL-RSs of both indicated TCI states for QCL Type A, excluding the QCL parameters {Doppler shift, Doppler spread} of the second indicated joint TCI state.

[0035] <<PUCCH>> The one or more TCI states applied to PUCCH may be based on the following. ◆ applyIndicatedTCIState={first TCI state, second TCI state, both} is configured for each PUCCH resource / resource group.

[0036] <<PUSCH>> The one or more TCI states applied to PUSCH may be based on the following. ◆ For dynamic grant (DG) / configured grant (CG) PUSCH, the indicated TCI state is always applied. -◆ For PUCCH scheduled / activated by DCI format 0_0, the indicated TCI state is always applied. -◆ For Type 1 CG PUSCH, applyIndicatedTCIState={first TCI state, second TCI state, both} is configured. -◆ The SRS resource set indicator field indicates one or both SRS resource sets to be used.

[0037] <<SRS>> The one or more TCI states applied to SRS may be based on the following. ◆For A-SRS for beamManagement, or A / SP / P-SRS for codebook, nonCodebook or antennaSwitching, when the SRS resource set is configured with followUnifiedTCI-StateSRS, applyIndicatedTCIState={first TCI state, second TCI state, both} is configured to indicate which indicated TCI state is applied for each SRS resource set. For other SRS, the configured TCI state in the SRS resource set is applied.

[0038] <Application of Indicated TCI in Rel.18 (mDCI mTRP)> In mDCI mTRP, the application of the indicated TCI state may be based on the following.

[0039] <<PDCCH>> One or more TCI states applied to PDCCH may be based on the following: ◆ If followUnifiedTCIState is set for CORESET0, the indicated TCI state is applied. Otherwise, the Rel. 15 specification is applied. That is, the applied TCI state is the TCI state activated by MAC CE, or QCL'd with SSB. ◆ For CORESETs other than index 0 that have only USS / CSS type 3, the indicated TCI state is always applied. ◆ For CORESETs other than index 0 that have at least CSS other than CSS type 3, if followUnifiedTCIState is set, the indicated TCI state is applied. Otherwise, the configured TCI state of that CORESET is applied. ◆The TCI state specified for coresetPoolIndex={0,1} is applied to the corresponding CORESET. <<PDSCH>> One instruction TCI state is always applied to a PDSCH. The one TCI state applied to a PDCCH may be based on the following: ◆The TCI state specified for coresetPoolIndex={0,1} is applied to the PDSCH scheduled / activated by the corresponding CORESET.

[0040] <<CSI-RS>> A single TCI state applied to a CSI-RS may be based on the following: ◆When followUnifiedTCIState is set for an A-CSI-RS for CSI acquisition or beam management, applyIndicatedTCIState={first TCI state, second TCI state, or both} is set for each CSI-RS resource set or for each CSI-RS resource to indicate which indicated TCI state should be applied. For other CSI-RSs, the set TCI state for that CSI-RS is applied. ◆The first or second indicated TCI state corresponds to the TCI state specified for coresetPoolIndex={0,1}, respectively.

[0041] <<PUCCH>> A single TCI state applied to PUCCH may be based on the following: ◆ For each PUCCH resource / resource group, applyIndicatedTCIState={first TCI state, second TCI state, or both} is set.

[0042] <<PUSCH>> A single TCI state applied to a PUSCH may be based on the following: ◆ For dynamic grant (DG) / configured grant (CG) PUSCHs, the indicated TCI state is always applied. —◆ For DG PUSCHs and Type 2 CG PUSCHs, the first or second indicated TCI state corresponding to the TCI state specified for coresetPoolIndex={0,1} is applied, respectively. —◆ For Type 1 CG PUSCHs, applyIndicatedTCIState={first TCI state, second TCI state, or both} is set.

[0043] <<SRS>> A single TCI state applied to an SRS may be based on the following: ◆If the SRS resource set for an A-SRS for beamManagement, or an A / SP / P-SRS for a codebook, nonCodebook, or antennaSwitching is set to followUnifiedTCI-StateSRS, applyIndicatedTCIState={first TCI state, second TCI state, or both} is set for each SRS resource set to indicate which indicated TCI state to apply. For other SRSs, the configured TCI state in the SRS resource set is applied. —◆The first or second indicated TCI state corresponds to the TCI state specified for coresetPoolIndex={0,1}, respectively. —◆If applyIndicatedTCIState is not set for an A-SRS, the indicated TCI state specified for the coresetPoolIndex of the triggering PDCCH is applied. ―◆For SRS for codebooks or noncodebooks, the first and second instruction TCI states are applied to the first and second SRS resource sets, respectively.

[0044] <TCI Instructions in Rel. 18> The setting of TCI states by RRC is based on the following: ◆ Up to 128 TCI states can be set for a single serving cell. In coordination between multiple TRPs with different PCIs, multiple TCI states can be associated with the SSBs of different PCIs, and up to 8 PCIs can be set.

[0045] MAC CE activation of TCI states is based on the following: ◆ In single TRP transmission, up to eight TCI states can be activated for one serving cell or for one BWP of one serving cell. In switching between multiple TRPs with different PCIs, multiple activated TCI states can be associated with the SSBs of different PCIs, and up to eight PCI TCI states can be activated. ◆ In multi-TRP joint transmission, up to eight TCI states can be activated per TRP / cell, and up to sixteen TCI states can be activated in total. In joint transmission using multiple TRPs with different PCIs, multiple activated TCI states can be associated with the SSBs of different PCIs, and up to two PCI TCI states can be activated.

[0046] DCI's indication of TCI states is based on the following: ◆ Multiple code points in the TCI indication field within DCI are mapped to multiple TCI states activated via MAC CE. ◆ In a single TRP transmission, one code point in the TCI indication field within DCI is mapped to one DL and UL joint TCI, or one DL TCI and one UL TCI, or one DL TCI, or one UL TCI. ◆ In a single DCI-based multi-TRP joint transmission, one code point in the TCI indication field within DCI is mapped to one or two DL and UL joint TCIs, or one or two DL TCIs and one or two UL TCIs, or one or two DL TCIs, or one or two UL TCIs. ◆In multi-DCI-based multi-TRP joint transmission, one code point in the TCI instruction field within the DCI is mapped to one or two DL and UL joint TCIs, or one or two DL TCIs and one or two UL TCIs, or one or two DL TCIs, or one or two UL TCIs. Multiple DCIs indicate TCI states for multiple TRPs.

[0047] In Rel. 18, the unified TCI state for single TRP (sTRP) has been extended to support multi-TRP (mTRP) in Rel. 16-18 as follows: ◆mTRP based on single DCI (sDCI). —◆Rel. 16 sDCI mTRP PDSCH (NCJT, repeating). —◆Rel. 17 sDCI mTRP PUSCH / PUCCH / PDCCH repeating. —◆Rel. 17 SFN-PDCCH / PDSCH. —◆Rel. 18 PDSCH-CJT. —◆Rel. 18 sDCI simultaneous transmission with multiple panels (STxMP) PUSCH / PUCCH. ◆mTRP based on multi-DCI (mDCI). —◆Rel. 16 mDCI mTRP PDSCH (NCJT). ―◆Rel. 18 mDCI STxMP PUSCH / PUCCH.

[0048] In the Rel. 18 Unified TCI Framework, the following is assumed: ◆ RRC-based switching between joint TCI states and separate UL and DL TCI states. ◆ The TI state list set by the RRC is common among multiple TRPs. Both CC-specific TCI pools and CC-common TCI pools from Rel. 17 are supported. ◆ TCI state ID indications based on MAC CE / DCI in the CC list from Rel. 17 are reused. ◆ Beam application timing (BAT) from Rel. 17 is reused.

[0049] In sDCI mTRP, one DCI / MAC CE indicates a joint TCI state, or up to two sets of UL and DL TCI states. This indication may be based on the following:

[0050] ◆The TCI field in DCI format 1_2 / 1_2 [with or without DL assignment] indicates a first and at least one second TCI state. If only one TCI state (e.g., the second TCI state) is indicated, the UE updates the indicated TCI state and maintains the other TCI state (e.g., the first TCI state). If two TCI states are indicated, the UE updates both TCI states.

[0051] ◆Once two TCI states are indicated, the UE maintains both indicated TCI states. However, this does not mean that both indicated TCI states are always applied to all channels / RSs. Which of the indicated TCI states applies to each channel / RS is defined in the specification, set by the RRC, or indicated by the DCI.

[0052] In mDCI mTRP, PDSCH scheduled / activated by DCI format 1_1 / 1_2 may be based on the following:

[0053] ◆A new 2-bit TCI selection field in the scheduling / activation DCI format 1_1 / 1_2 can indicate which one or two indicated TCI states will be applied to the PDSCH being scheduled / activated. This enables dynamic switching between sTRP PDSCH and mTRP PDSCH by the scheduling / activation DCI. The values ​​00, 01, 10, and 11 of the TCI selection field correspond to the first TCI state, the second TCI state, the first and second TCI states, and the reserved value, respectively. For example, if the TCI selection field indicates 00, the sTRP PDSCH using the first TCI state will be scheduled / activated.

[0054] ◆However, this TCI selection behavior requires the UE to buffer the two beams before the end of DCI decoding in FR2, because the UE does not know the value of the TCI selection field before DCI decoding. This TCI selection behavior is applicable when the UE capability of the two default beams in FR2 is reported, or when the UE capability of the two default beams in sDCI mTRP is not reported in FR2 and the scheduling offset is greater than the threshold timeDurationForQCL, or when it is FR1.

[0055] ◆In a PDSCH scheduled / activated by DCI format 1_0 / 1_1 / 1_2, if the scheduling offset is less than or equal to the threshold timeDurationForQCL, and the UE does not support the two default TCI states in sDCI mTRP in FR2, the first TCI state is always applied.

[0056] <Rel. 18 Procedure for TCI states (Antenna port pseudo-collocation)> When the UE is configured with dl-OrJointTCI-StateList and has two indicated TCI states, there are several cases x as follows:

[0057] ◆Case 1: When the UE operates in FR1, or when the UE reports the capability of defaultQCL-TwoTCI in FR2, regardless of the offset between the reception of the scheduling DCI format 1_0 / 1_1 / 1_2 and the reception of the PDSCH to be scheduled / activated.

[0058] ◆Case 2: When the UE has not reported the ability of defaultQCL-TwoTCI in FR2, and the scheduling offset between the reception of scheduling DCI format 1_0 / 1_1 / 1_2 and the reception of the scheduled / activated PDSCH is greater than or equal to timeDurationForQCL.

[0059] In Case 1 or Case 2, the UE operates according to the following procedure Bx.

[0060] ―◆Procedure B1 The UE can be configured by the upper layer parameter applyIndicatedTCI-StateDCI-1-0 to indicate which of the one or more indicated TCI states—the first indicated TCI state, the second indicated TCI state, or both indicated TCI states—will be applied to the PDSCH receiver scheduled or activated by DCI format 1_0. If the UE is configured with cjt-Scheme-PDSCH and reports twoTCI-StatePDSCH-CJT-TxScheme, or if the UE is configured with sfnSchemePdsch, the UE can be configured with applyIndicatedTCI-StateDCI-1-0 having only the value both, which points to both indicated TCI states. In this case, the UE applies both instruction TCI states to PDSCH receptions scheduled or activated by DCI format_0 on search spaces other than Type0 / 0A / 2 on CORESET#0.

[0061] ―◆Procedure B2 If the UE is not set to applyIndicatedTCI-StateDCI-1-0, the first indicated TCI state is applied to the PDSCH receiver scheduled or activated by DCI format 1_0.

[0062] ―◆Procedure B3 If the UE has jointly configured tciSelection-PresentInDCI for both DCI formats 1_1 and 1_2 within the same DL BWP, and the UE is receiving DCI format 1_1 / 1_2 to schedule or activate PDSCH reception, the UE determines one or more instruction joint / DL TCI states for PDSCH reception according to some of the following procedures B3-x.

[0063] --◆Procedure B3-1 If the DCI format 1_1 / 1_2 indicates code point "00" in the TCI selection field, the UE applies the first of the two indicated joint / DL TCI states to all PDSCH DM-RS for the corresponding PDSCH transmission occasions scheduled or activated by the DCI format 1_1 / 1_2.

[0064] --◆Procedure B3-2 If the DCI format 1_1 / 1_2 indicates code point "01" in the TCI selection field, the UE applies the second of the two indicated joint / DL TCI states to all PDSCH DM-RS for the corresponding PDSCH transmission occasions scheduled or activated by the DCI format 1_1 / 1_2.

[0065] --◆Procedure B3-3 If the DCI format 1_1 / 1_2 indicates code point "11" in the TCI selection field, the UE applies both indicated joint / DL TCI states to all PDSCH DM-RS for the corresponding PDSCH transmission occasions scheduled or activated by the DCI format 1_1 / 1_2.

[0066] ―◆Procedure B4 If the UE is not configured with tciSelection-PresentInDCI, and the UE is receiving DCI format 1_1 / 1_2 to schedule or activate PDSCH reception, the UE applies both instruction TCI states to the scheduled or activated PDSCH reception.

[0067] <UE Procedure for Determining PDCCH Assignment> Control Physical Layer Procedure / UE Procedure for Receiving Control Information <<Monitoring Occasion of PDCCH Candidates>> The determination of the monitoring occasion for one or more PDCCH candidates in a search space set with index 0 (search space #0, SS #0) is based on the following procedure C1.

[0068] ◆Procedure C0: If a UE is provided with a zero value for searchSpaceID in PDCCH-ConfigCommon for a type 0 / 0A / 1A / 2-PDCCH CSS set, and the UE determines the monitoring occasions for one or more PDCCH candidates of a type 0 / 0A / 1A / 2-PDCCH CSS set [as described in the specification for the control physical layer procedure], and the UE is provided with C-RNTI, then the UE monitors one or more PDCCH candidates only in the monitoring occasions associated with the SS / PBCH block. The SS / PBCH block is determined by the most recent of the following multiple events C0-x: ―◆Event C0-1: A MAC CE activation command indicating one TCI-State of an active BWP containing a CORESET (CORESET#0) with index 0 [as described in the specification for the physical layer procedure for data]. The TCI-State contains a CSI-RS that is QCL'd with its SS / PBCH block. ―◆Event C0-2: A random access procedure not initiated by a PDCCH order that triggers a contention-free random access procedure. ―◆Event C0-3: A configured grant-based PUSCH transmission within the RRC_INACTIVE state [as described in the specification for the physical layer procedure for control].

[0069] In the example in Figure 1, the UE determines SS / PBCH block #1 for PRACH in a random access procedure [not initiated by a PDCCH order that triggers a no-conflict random access procedure], and then receives a MAC CE activation command indicating the TCI state of the active BWP, including CORESET #0. In this example, the UE determines the monitoring occasions associated with SS / PBCH block #2 that are QCL'd with CSI-RS included in the TCI state, as monitoring occasions for one or more PDCCH candidates of SS#0.

[0070] <<QCL assumption for PDCCH>> The QCL assumption for the DMRS antenna port for PDCCH reception within CORESET is based on the following procedure Ax.

[0071] ◆Procedure A1: For a CORESET with index 0, several procedures A1-x are defined below.

[0072] ―◆Procedure A1-1: If a UE is provided with a TCI-State and a followUnifiedTCI-State for its CORESET, the UE assumes that the DMRS antenna ports for one or more PDCCH receivers in its CORESET and the DMRS antenna ports for one or more PDSCHs scheduled by one or more DCI formats provided by the PDCCH receivers in its CORESET are quasi co-located (QCLed) with the reference signals provided by the indicated TCI-State [in the specification of the control physical layer procedure].

[0073] ―◆Procedure A1-2: In all other cases (when not in procedure A1-1), if the UE is provided with dl-OrJointTCI-StateList, and the first TCI-State and second TCI-State are specified, and applyIndicatedTCI-State for its CORESET is provided, the UE will operate based on some of the following procedures A1-2-x.

[0074] ---◆Procedure A1-2-1: If the CORESET is associated with a type 0 / 0A / 2-PDCCH CSS set having search space set index 0, the UE operates based on some of the following procedures A1-2-1-x. ---◆Procedure A1-2-1-1: If applyIndicatedTCI-State = 'first', the UE assumes that the DM-RS antenna port for PDCCH reception in the CORESET is QCL'd with one or more reference signals provided by the first TCI-State. ---◆Procedure A1-2-1-2: If applyIndicatedTCI-State = 'second', the UE assumes that the DM-RS antenna port for PDCCH reception in the CORESET is QCL'd with one or more reference signals provided by the second TCI-State. ---◆Procedure A1-2-1-3: If applyIndicatedTCI-State = 'none', the UE assumes that the DM-RS antenna port for PDCCH reception in that CORESET is QCL'd with one or more DL RS configured by the TCI state. If there is a MAC CE activation command for that CORESET, the TCI state is indicated by that MAC CE activation command.

[0075] ---◆Procedure A1-2-2: Otherwise (if not Procedure A1-2-1), the UE operates based on some of the following Procedures A1-2-2-x. ---◆Procedure A1-2-2-1: If applyIndicatedTCI-State = 'first', the UE assumes that the DM-RS antenna port for PDCCH reception in its CORESET is QCL'd with one or more reference signals provided by the first TCI-State. ---◆Procedure A1-2-2-2: If applyIndicatedTCI-State = 'second', the UE assumes that the DM-RS antenna port for PDCCH reception in its CORESET is QCL'd with one or more reference signals provided by the second TCI-State. ---◆Procedure A1-2-2-3: If applyIndicatedTCI-State = 'both', the UE assumes that the DM-RS antenna port for PDCCH reception in the CORESET is QCL'd with multiple reference signals provided by the first TCI-State and the second TCI-State. ---◆Procedure A1-2-2-4: If applyIndicatedTCI-State = 'none', the UE assumes that the DM-RS antenna port for PDCCH reception in the CORESET is QCL'd with one or more DL RSs set by the TCI state. The TCI state is indicated by the MAC CE activation command for the CORESET.

[0076] ―◆Procedure A1-3: Otherwise (if neither Procedure A1-1 nor Procedure A1-2), the UE assumes that the DMRS antenna port for PDCCH reception in its CORESET is QCL'd with one of the following signals A1-3-x. ―◆Signal A1-3-1: One or more DL RSs, if any, set by the TCI state. The TCI state is indicated by the MAC CE activation command for that CORESET. --◆Signal A1-3-2: If no MAC CE activation commands indicating the TCI state for that CORESET have been received after the most recent random access procedure not initiated by a PDCCH order that triggers a contention-free random access procedure, then the SS / PBCH block identified by the UE during the most recent random access procedure, or the SS / PBCH block identified by the UE during the most recent setting grant PUSCH transmission.

[0077] <<TCI status for CORESET>> The TCI status for CORESET is based on the following procedure Dx.

[0078] ◆Procedure D1: If a UE is provided with a single TCI state for a CORESET other than the CORESET having index 0, or if the UE has received a MAC CE activation command for one or two of the multiple TCI states provided for the CORESET, the UE assumes that the DM-RS ports associated with one or more PDCCH receptions within that CORESET are QCL'd with one or more DL RSs configured by that one or more TCI states.

[0079] ◆Procedure D2: For a CORESET having index 0, the UE assumes that one CSI-RS is provided by the SS / PBCH block, which has a qcl-Type set to 'typeD' in one TCI state as indicated by the MAC CE activation command for that CORESET.

[0080] <Terminology> In this disclosure, the following abbreviations may be used: ◆Single frequency network (SFN) ◆Coherent joint transmission (CJT)

[0081] (Analysis) Procedure C is unclear under Rel. 17 Unified TCI Framework. Therefore, it is being considered that the aforementioned event C0-1 may be modified to the following event C0-1a. —◆Event C0-1a: If the UE is provided with followUnifiedTCI-State for a CORESET having index 0, a TCI-State indicated [as described in the specification for the physical layer procedure for control] that includes one CSI-RS associated with the SS / PBCH block; otherwise, a MAC CE activation command indicating one TCI state (TCI-State) of the active BWP including a CORESET having index 0, as described in the specification. That TCI-State includes a CSI-RS that is QCL'd with the SS / PBCH block.

[0082] In the Rel. 18 Unified TCI Framework, two TCI states are indicated, and one or both of these two TCI states are applied to the channels / RS of each DL / UL. For PDCCH, applyIndicatedTCI-State is set for each CORESET to indicate which one or both TCI states are applied to that CORESET. Note that applyIndicatedTCI-State = 'both' is for PDCCH-SFN and therefore does not apply to CORESET #0 and SS #0.

[0083] However, event C0-1a does not consider the case where two TCI states are indicated. If the procedure for this case is not clear, communication quality / throughput may be reduced.

[0084] Therefore, the inventors devised a method for determining the monitoring occasions for PDCCH candidates.

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

[0086] (Various substitutions) In this disclosure, words enclosed in parentheses () may indicate an explanation of the preceding word (e.g., an explanation of spelling), a paraphrase, a specific example, or supplementary explanation. Also, in this disclosure, words enclosed in square brackets [] may be interpreted as part of the overall meaning of the text, or they may be interpreted as being excluded (ignored). Note that parentheses () and square brackets [] may be used for purposes / meanings other than those described above.

[0087] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0088] In this disclosure, terms such as notice, activate, deactivate, indicate (or specify), select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and capable of operating may be interpreted interchangeably.

[0089] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Elements (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.

[0090] In this disclosure, the upper layer signaling may be any or a combination thereof, such as Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and other messages (e.g., messages from the core network, such as positioning protocol messages (e.g., NR Positioning Protocol A (NRPPPa) / LTE Positioning Protocol (LPP)) messages).

[0091] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).

[0092] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).

[0093] In this disclosure, ceil(x), the ceiling function, and the ceiling function may be interpreted as interchangeable. In this disclosure, floor(x), the floor function, and the floor function may be interpreted as interchangeable. In this disclosure, ceil(x) and floor(x) may be interpreted as interchangeable. In this disclosure, sqrt(x), the square root of x, and the root x may be interpreted as interchangeable. In this disclosure, x mod y, mod(x, y), the mod function, and the modulo operation may be interpreted as interchangeable. In this disclosure, Σi=M M+N-1 f(i), Σ i=M M+N-1 f i , f(i) over i = M, M+1, ..., M+N-1 or f i the summation thereof, 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 for selecting k values from n values, combinatorial coefficient, binomial coefficients, n C k , C n k may be read interchangeably. In the present disclosure, x / / y and floor(x / y) may be read interchangeably.

[0094] In the present disclosure, A b , A_b, Ab, and the notation with b attached to the lower right of A may be read interchangeably. In the present disclosure, A c , A^c, and the notation with c attached to the upper right of A may be read interchangeably. In the present disclosure, A b c , A_b^c, and the notation with b attached to the lower right of A and c attached to the upper right of A may be read interchangeably. In the present disclosure, x ~ may be represented by adding ~ on x, and may be referred to as x tilde. In the present disclosure, x - may be represented by adding - on x, and may be referred to as x bar. In the present disclosure, x ^ may be represented by adding ^ on x, and may be referred to as x hat.

[0095] In this disclosure, FR may be at least one of FR1, FR2, FR2-1, FR2-2, FR3, subterahertz, and terahertz. In this disclosure, the frequency range corresponding to FR1 may be 410–7125 MHz. In this disclosure, FR2 may include FR2-1 and FR2-2, 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.

[0096] (Wireless communication method) In this disclosure, search space (SS)[set]#0, SS[set] having index 0, type 0 / 0A / 1A / 2-PDCCH CSS set which is provided with a zero value for searchSpaceID in PDCCH-ConfigCommon, and SS[set] associated with CORESET#0 may be interpreted as one another.

[0097] In this disclosure, CORESET#0, CORESET having index 0, and CORESET associated with SS[set]#0 may be interpreted as mutually exclusive.

[0098] In this disclosure, a random access procedure [not initiated by a PDCCH order that triggers a contention-free random access procedure] and a contention-based random access procedure may be interpreted as each other.

[0099] In this disclosure, the following terms may be used interchangeably: ◆ Event / information / state / procedure / transmission / reception / setting / instruction / update; ◆ At least one of the following: TCI state [instruction / update], MAC CE activation command [reception], random access procedure, and PUSCH transmission.

[0100] In this disclosure, the following terms may be used interchangeably: ◆ Rel. 18 Unified TCI Framework; ◆ Rel. 18 Behavior; ◆ At least one of the following: the UE is provided with followUnifiedTCI-State for a CORESET [having index 0], and is indicated with a first TCI-State and a second TCI-State; the UE is provided with applyIndicatedTCI-State [set to 'first' or 'second'] for a CORESET [having index 0]; and the UE is provided with dl-OrJointTCI-StateList.

[0101] In this disclosure, the following terms may be used interchangeably: ◆ Rel. 17 Unified TCI Framework. ◆ Rel. 17 Behavior. ◆ At least one of the following: the UE is provided with followUnifiedTCI-State for a CORESET [with index 0], the UE is not provided with applyIndicatedTCI-State for a CORESET [with index 0], or the UE is provided with dl-OrJointTCI-StateList.

[0102] In this disclosure, the following terms may be interpreted as interchangeable: ◆Rel. 15 TCI framework; ◆Rel. 15 behavior; ◆At least one of the following: not providing followUnifiedTCI-State for a CORESET [having index 0], and the UE not providing dl-OrJointTCI-StateList.

[0103] <Embodiment 1> Embodiment 1 relates to determining the monitoring occasion for one or more PDCCH candidates of SS#0.

[0104] Procedure C0 may be modified to cover the following three cases:

[0105] ◆Case 1: Rel. 18 Unified TCI Framework If a UE is provided with dl-OrJointTCI-StateList (and at least one followUnifiedTCI-State for CORESET#0) and has indicated a first TCI-State and a second TCI-State, and has provided applyIndicatedTCI-State[='first' or 'second'] for CORESET#0, then the monitoring occasions for one or more PDCCH candidates of type 0 / 0A / 1A / 2-PDCCH CSS set may be monitoring occasions associated with an SS / PBCH block associated with (determined by one indicated TCI state) that is determined / selected / identified by applyIndicatedTCI-Stat set in CORESET#0 (for CORESET#0).

[0106] ◆Case 2: Rel. 17 Unified TCI Framework If a UE is provided with dl-OrJointTCI-StateList (and at least one followUnifiedTCI-State for CORESET#0) and has one TCI-State indicated (but is not provided with applyIndicatedTCI-State for CORESET#0), then the monitoring occasions for one or more PDCCH candidates of type 0 / 0A / 1A / 2-PDCCH CSS set may be the monitoring occasions for an SS / PBCH block associated with one indicated TCI state for CORESET#0 (determined by one indicated TCI state) (or determined by the aforementioned event C0-1a).

[0107] ◆Case 3: Rel. 15 TCI Framework If the UE does not provide dl-OrJointTCI-StateList (followUnifiedTCI-State for CORESET#0), the monitoring occasions for one or more PDCCH candidates of type 0 / 0A / 1A / 2-PDCCH CSS set may be the monitoring occasions associated with a MAC CE activation command, a random access procedure, or an SS / PBCH block associated with a TCI state in a configured grant PUSCH (determined by that TCI state) (or determined by the procedure C0 described above).

[0108] The UE may receive a setting for a CORESET (CORESET#0) having index 0. The UE may receive one or more TCI state indications (MAC CE / DCI). The BS may transmit the setting / indication. If the one or more TCI states are two TCI states (a first TCI-State and a second TCI-State), and the setting includes a first parameter (applyIndicatedTCI-State) for determining one of the two TCI states ('first' or 'second'), the UE / BS may determine a monitoring occasion for one or more PDCCH candidates in a search space (SS#0) having index 0, based on a synchronization signal block (SS / PBCH block) referenced by the one TCI state. The BS may transmit one or more PDCCHs in that monitoring occasion.

[0109] According to Embodiment 1, even when the Unified TCI Framework of Rel. 18 / Rel. 17 is applied, the UE can appropriately determine the monitoring occasions for PDCCH candidates.

[0110] Embodiment 1 may be defined in the specifications based on one of the following multiple specific examples x.

[0111] <<Specific Example 1>> Procedure C0 may be modified as follows: Procedure C1.

[0112] ◆Procedure C1: If a UE is provided with a zero value for searchSpaceID in PDCCH-ConfigCommon for a type 0 / 0A / 1A / 2-PDCCH CSS set, and the UE determines the monitoring occasions for one or more PDCCH candidates of a type 0 / 0A / 1A / 2-PDCCH CSS set [as described in the specification for the control physical layer procedure], and the UE is provided with C-RNTI, then the UE monitors one or more PDCCH candidates only in the monitoring occasions associated with the SS / PBCH block. The SS / PBCH block is determined by the most recent one of the following multiple events C1-x:

[0113] ―◆Event C1-01: If the UE is provided with followUnifiedTCI-State for a CORESET having index 0, and is provided with a first TCI-State and a second TCI-State, and is provided with applyIndicatedTCI-State [set to 'first' or 'second'] for that CORESET, then the indicated TCI state (TCI-State) [indicated / updated] is associated with the applyIndicatedTCI-State for that CORESET (determined / selected / identified by the applyIndicatedTCI-State). The TCI-State includes the CSI-RS which is QCL'd with its SS / PBCH block.

[0114] ―◆Event C1-02: [In other cases (when the conditions of Event C1-01 are not met),] if the UE is provided with followUnifiedTCI-State for a CORESET having index 0 and is not provided with applyIndicatedTCI-State for that CORESET, then the indicated TCI-State [indication / update] includes the CSI-RS that is QCL'd with the SS / PBCH block.

[0115] ―◆Event C1-1: [Otherwise (when neither the conditions of Event C1-01 nor Event C1-02 are met),] [as described in the specification for the physical layer procedure for data,] a MAC CE activation command that indicates one TCI state (TCI-State) of an active BWP containing a CORESET with index 0. That TCI-State contains a CSI-RS that is QCL'd with its SS / PBCH block.

[0116] ―◆Event C1-2: [Otherwise (if neither the conditions of Event C1-01 nor Event C1-02 are met),] A random access procedure not initiated by a PDCCH order that triggers a random access procedure without conflict.

[0117] ―◆Event C1-3: [Otherwise (when neither the conditions of Event C1-01 nor Event C1-02 are met),] [as described in the specifications of the control physical layer procedure,] setting grant-based PUSCH transmission within the RRC_INACTIVE state.

[0118] <<Specific Example 2>> Procedure C0 may be modified as follows: Procedure C2.

[0119] ◆Procedure C2: If a UE is provided with a zero value for searchSpaceID in PDCCH-ConfigCommon for a type 0 / 0A / 1A / 2-PDCCH CSS set, and the UE determines the monitoring occasions for one or more PDCCH candidates of a type 0 / 0A / 1A / 2-PDCCH CSS set [as described in the specification for the physical layer procedure for control], and the UE is provided with C-RNTI, then the UE monitors one or more PDCCH candidates only in the monitoring occasions associated with the SS / PBCH block. The SS / PBCH block is determined by the most recent of the following multiple events C2-x:

[0120] ―◆Event C2-01: [If the UE is provided with followUnifiedTCI-State for a CORESET having index 0, then] the indication / update of the appliedIndicatedTCI-State associated with (determined / selected / identified by) the applyIndicatedTCI-State [set to 'first' or 'second'] for the CORESET having index 0. The TCI-State includes the CSI-RS which is QCL'd with its SS / PBCH block.

[0121] ―◆Event C2-02: [In other cases (when the conditions of Event C2-01 are not met),] if the UE has provided a followUnifiedTCI-State for a CORESET having index 0, the indicated TCI-State [indication / update] includes the SS / PBCH block and the QCL-bound CSI-RS.

[0122] ―◆Event C2-1: [Otherwise (when neither the conditions of Event C2-01 nor Event C2-02 are met),] [as described in the specification for the physical layer procedure for data,] a MAC CE activation command that indicates one TCI state (TCI-State) of an active BWP containing a CORESET with index 0. That TCI-State contains a CSI-RS that is QCL'd with its SS / PBCH block.

[0123] ―◆Event C2-2: [Otherwise (if neither the conditions of Event C2-01 nor Event C2-02 are met),] A random access procedure not initiated by a PDCCH order that triggers a random access procedure without conflict.

[0124] ―◆Event C2-3: [Otherwise (when neither the conditions of Event C2-01 nor Event C2-02 are met),] [as described in the specifications of the control physical layer procedure,] setting grant-based PUSCH transmission within the RRC_INACTIVE state.

[0125] <<Specific Example 3>> Procedure C0 may be modified as follows: Procedure C3.

[0126] ◆Procedure C3: If a UE is provided with a zero value for searchSpaceID in PDCCH-ConfigCommon for a type 0 / 0A / 1A / 2-PDCCH CSS set, and the UE determines the monitoring occasions for one or more PDCCH candidates of a type 0 / 0A / 1A / 2-PDCCH CSS set [as described in the specification for the physical layer procedure for control], and the UE is provided with C-RNTI, then the UE monitors one or more PDCCH candidates only in the monitoring occasions associated with the SS / PBCH block. The SS / PBCH block is determined by the most recent of the following multiple events C3-x:

[0127] ―◆Event C3-0: If the UE is provided with a followUnifiedTCI-State for a CORESET having index 0, the TCI-State [instruction / update] is instructed [as described in the specification for the physical layer procedure for data], including the CSI-RS that is QCL'd with the SS / PBCH block.

[0128] ―◆Event C3-1: [Otherwise (if the conditions of Event C3-0 are not met),] [as described in the specification for the physical layer procedure for data,] a MAC CE activation command that indicates one TCI state (TCI-State) of an active BWP containing a CORESET with index 0. That TCI-State contains a CSI-RS that is QCL'd with its SS / PBCH block.

[0129] ―◆Event C3-2: [Otherwise (if the conditions of Event C3-0 are not met),] a random access procedure not initiated by a PDCCH order that triggers a random access procedure without conflict.

[0130] ―◆Event C3-3: [Otherwise (if the conditions of Event C3-0 are not met),] [as described in the specifications of the control physical layer procedure,] setting grant-based PUSCH transmission within the RRC_INACTIVE state.

[0131] <<Specific Example 4>> Procedure C0 may be modified as follows: Procedure C4.

[0132] ◆Procedure C4: If a UE is provided with a zero value for searchSpaceID in PDCCH-ConfigCommon for a type 0 / 0A / 1A / 2-PDCCH CSS set, and the UE determines the monitoring occasions for one or more PDCCH candidates of a type 0 / 0A / 1A / 2-PDCCH CSS set [as described in the specification for the control physical layer procedure], and the UE is provided with C-RNTI, then the UE monitors one or more PDCCH candidates only in the monitoring occasions associated with the SS / PBCH block. The SS / PBCH block is determined by one of the following events C4-x:

[0133] ―◆Event C4-1: If the UE is provided with a followUnifiedTCI-State for a CORESET having index 0, and is provided with a first TCI-State and a second TCI-State, and is provided with an applyIndicatedTCI-State set to 'first' or 'second' for that CORESET, then the most recent indicated TCI state (TCI-State) associated with the applyIndicatedTCI-State for that CORESET (determined / selected / identified by that applyIndicatedTCI-State) is indicated / updated. That TCI-State includes the CSI-RS that is QCL'd with its SS / PBCH block.

[0134] ―◆Event C4-2: In all other cases (when the conditions of Event C4-1 are not met), if the UE is provided with followUnifiedTCI-State for a CORESET having index 0, and is not provided with applyIndicatedTCI-State for that CORESET, then the most recent indicated TCI-State [indication / update], including the CSI-RS that is QCL'd with the SS / PBCH block.

[0135] ―◆Event C4-3: Otherwise (when neither the conditions of Event C4-1 nor Event C4-2 are met), the most recent of the following multiple Events C4-3-x. ―◆Event C4-3-1: A MAC CE activation command indicating one TCI-State of an active BWP containing a CORESET with index 0 [as described in the specification for data physical layer procedures]. That TCI-State contains its SS / PBCH block and QCL-enabled CSI-RS. ―◆Event C4-3-2: A random access procedure not initiated by a PDCCH order that triggers a random access procedure without conflict. ―◆Event C4-3-3: A setting grant-based PUSCH transmission within the RRC_INACTIVE state [as described in the specification for control physical layer procedures].

[0136] <<Specific Example 5>> Procedure C0 may be modified as follows: Procedure C5.

[0137] ◆Procedure C5: If a UE is provided with a zero value for searchSpaceID in PDCCH-ConfigCommon for a type 0 / 0A / 1A / 2-PDCCH CSS set, and the UE determines the monitoring occasions for one or more PDCCH candidates of a type 0 / 0A / 1A / 2-PDCCH CSS set [as described in the specification for the control physical layer procedure], and the UE is provided with C-RNTI, then the UE monitors one or more PDCCH candidates only in the monitoring occasions associated with the SS / PBCH block. The SS / PBCH block is determined by one of the following events C5-x:

[0138] ―◆Event C5-1: If the UE is provided with followUnifiedTCI-State for a CORESET having index 0, and is provided with a first TCI-State and a second TCI-State, and is provided with applyIndicatedTCI-State set to 'first' or 'second' for that CORESET, then the most recent of the following multiple Events C5-1-x: ―◆Event C5-1-0: An indication / update of an indicated TCI state (TCI-State) associated with the applyIndicatedTCI-State for that CORESET (determined / selected / identified by that applyIndicatedTCI-State). That TCI-State includes a CSI-RS that is QCL'd with its SS / PBCH block. --◆Event C5-1-1: A MAC CE activation command that indicates one TCI-State of an active BWP containing a CORESET with index 0 [as described in the specification for the physical layer procedure for data]. That TCI-State contains its SS / PBCH block and QCL-enabled CSI-RS. --◆Event C5-1-2: A random access procedure not initiated by a PDCCH order that triggers a random access procedure without conflict. --◆Event C5-1-3: A setting grant-based PUSCH transmission within the RRC_INACTIVE state [as described in the specification for the physical layer procedure for control].

[0139] ―◆Event C5-2: In all other cases (when the conditions of Event C5-1 are not met), if the UE is provided with followUnifiedTCI-State for a CORESET having index 0, and is not provided with applyIndicatedTCI-State for that CORESET, the most recent of the following multiple Events C5-2-x: ―◆Event C5-2-0: Indication / update of an indicated TCI-State, including its SS / PBCH block and QCL-enabled CSI-RS. ―◆Event C5-2-1: A MAC CE activation command indicating one TCI state (TCI-State) of an active BWP, including a CORESET having index 0, [as described in the specification for the physical layer procedure for data]. The TCI-State includes its SS / PBCH block and QCL-enabled CSI-RS. --◆Event C5-2-2: A random access procedure not initiated by a PDCCH order that triggers a random access procedure without conflict. --◆Event C5-2-3: A set grant-based PUSCH transmission within the RRC_INACTIVE state [as described in the specification for the control physical layer procedure].

[0140] ―◆Event C5-3: Otherwise (when neither the conditions of Event C5-1 nor Event C5-2 are met), the most recent of the following multiple Events C5-3-x. ―◆Event C5-3-1: A MAC CE activation command indicating one TCI-State of an active BWP containing a CORESET with index 0 [as described in the specification for the physical layer procedure for data]. That TCI-State contains its SS / PBCH block and QCL-enabled CSI-RS. ―◆Event C5-3-2: A random access procedure not initiated by a PDCCH order that triggers a random access procedure without conflict. ―◆Event C5-3-3: A setting grant-based PUSCH transmission within the RRC_INACTIVE state [as described in the specification for the physical layer procedure for control].

[0141] In the example in Figure 2, the UE determines SS / PBCH block #1 for PRACH in a random access procedure [not initiated by a PDCCH order that triggers a random access procedure without conflict], then sets followUnifiedTCI-State and applyIndicatedTCI-State set to 'second' for CORESET #0, and then directs the first TCI-State and second TCI-State. In this example, the UE determines the monitoring occasions associated with SS / PBCH block #2 that are QCL'd with CSI-RS contained in the second TCI-State determined by applyIndicatedTCI-State, among the first and second TCI-States, as monitoring occasions for one or more PDCCH candidates of SS#0.

[0142] <Embodiment 2> Embodiment 2 relates to the conditions under which Embodiment 1 applies.

[0143] Embodiment 1 may be applied only if at least one of the following is done: the corresponding UE capability is reported by the UE, and the corresponding RRC parameters are set. Otherwise, Rel. 15 behavior may be applied.

[0144] Common UE capability / RRC parameters for Rel. 17 behavior and Rel. 18 behavior in Embodiment 1 may be reported / set. Separate UE capability / RRC parameters for Rel. 17 behavior and Rel. 18 behavior in Embodiment 1 may be reported / set.

[0145] Rel. 18 behavior may also be the behavior of a UE when a UE is provided with a followUnifiedTCI-State for a CORESET having index 0, and is instructed to have a first TCI-State and a second TCI-State, and is provided with applyIndicatedTCI-State [set to 'first' or 'second'] for that CORESET. Rel. 17 behavior may also be the behavior of a UE when a UE is provided with a followUnifiedTCI-State for a CORESET having index 0, and is not provided with applyIndicatedTCI-State for that CORESET. Rel. 15 behavior may also be the behavior of a UE when a UE is not provided with a followUnifiedTCI-State for a CORESET having index 0.

[0146] According to Embodiment 2, the UE can perform appropriate procedures in response to UE capability [reporting] / RRC parameter [setting].

[0147] <Note> The above multiple embodiments / options / choices / variations may be combined to form a single embodiment / option / choice / variation.

[0148] In the embodiments described above, the measured RS may be a QCL source RS in an active TCI state / indicated / unified TCI state.

[0149] <<Notification of Information to UE / BS>> In the embodiments described above, notification of any information from the Network (NW) (e.g., Base Station (BS)) / NW node) to the UE / BS (in other words, reception of any information from the BS / NW node at the UE / BS) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE, NAS signaling, LPP messages, NRPPa messages), specific signals / channels (e.g., PDCCH, PDSCH, reference signals), or a combination thereof.

[0150] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new Logical Channel ID (LCID) not defined in existing standards in the MAC subheader.

[0151] If the above 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, or the format of the DCI.

[0152] Furthermore, the notification of arbitrary information to the UE / BS in the above-described embodiments may be periodic, semi-persistent, or aperiodic. Semi-persistent or aperiodic notification of information may be triggered by instructions from the UE / BS / NW.

[0153] In the embodiments described above, information from the network may be set / instructed by any or a combination thereof in the following ways: • Common to multiple UEs, or individual to each UE (per UE). • Common to multiple BSs, or individual to each BS (per BS). • Common to multiple frequencies (e.g., one or a combination thereof, such as cells, bands, band combinations, bandwidth parts (BWPs), component carriers, etc.) (e.g., common to cells), or frequency-specific (per frequency, e.g., per cell).

[0154] In the embodiments described above, the UE may receive at least one piece of information (QCL information) from the NW from among several of the following QCL rules / QCL types: ◆ 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 mean delay). ◆ QCL type D (spatial reception parameters).

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

[0156] In the embodiments described above, information from the network may be set / instructed by the following methods: ◆ Common to multiple UEs, or individual to a UE. ◆ Cell-specific, or common to multiple cells. ◆ Per UE / Per CC / Per BWP / Per band / Per cell / Per cell group (CG).

[0157] <<Notification of Information from UE / BS>> Notification of any information from UE / BS to the NW in the embodiments described above (in other words, transmission / reporting of any information from UE / BS to BS / NW nodes) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE, NAS signaling, LPP messages, NRPPa messages), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

[0158] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new LCID not specified in existing standards in the MAC subheader.

[0159] If the above notice is made by the UCI, the notice may be transmitted using PUCCH or PUSCH.

[0160] Furthermore, notifications of arbitrary information from the UE / BS in the above-described embodiments may be periodic, semi-persistent, or aperiodic. Semi-persistent or aperiodic notifications of information may be triggered by instructions from the UE / BS / NW.

[0161] <<Regarding the Application of Each Embodiment>> In a UE / BS, specific (e.g., one or more, or some) processing / operation / control / assumption / information for at least one of the embodiments described above may be applied (or used) if any or more of the following conditions are met: • A higher-layer parameter indicating the specific processing / operation / control / assumption / information is set in the UE / BS. • The specific processing / operation / control / assumption / information is determined in the UE / BS based on the relevant higher-layer parameter. • The specific processing / operation / control / assumption / information is designated / activated / triggered for the UE / BS by MAC CE / DCI / UCI / Resource / Channel / RS. • The UE / BS reports or supports a specific capability (e.g., UE capability) indicating (or related to) the specific processing / operation / control / assumption / information. • The application of the specific processing / operation / control / assumption / information is determined in the UE / BS based on specific conditions.

[0162] The above-mentioned specific capabilities may include at least one of the following: ◆ Supporting the above-mentioned specific processing / operation / control / assumption / information; ◆ Supporting the setting of followUnifiedTCI-State for CORESET; ◆ Supporting the setting of applyIndicatedTCI-State for CORESET.

[0163] In this disclosure, "to support" and "whether or not to support" may be interpreted interchangeably.

[0164] Furthermore, the above-mentioned specific capabilities may be capabilities that apply across all frequencies (commonly regardless of frequency), capabilities per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), capabilities per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), capabilities per subcarrier spacing (SCS), or capabilities per feature set (FS) or feature set per component-carrier (FSPC).

[0165] Furthermore, the specific capabilities described above may be capabilities that apply across all duplexing schemes (common to all duplexing schemes regardless of the duplexing scheme), or they may be capabilities specific to each duplexing scheme (e.g., Time Division Duplex (TDD), Frequency Division Duplex (FDD)).

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

[0167] (Note) The following inventions are added with respect to one embodiment of the present disclosure. <Note 1> A terminal having: a receiving unit that receives a setting of a control resource set having index 0 and an instruction for one or more transmission configuration indication (TCI) states; and a control unit that determines the monitoring occasion of one or more physical downlink control channel (PDCCH) candidates in a search space having index 0, based on a synchronization signal block referenced by the one TCI state, if the one or more TCI states are two TCI states and the setting includes a first parameter for determining one of the two TCI states. <Note 2> The terminal according to Note 1, wherein the setting includes a second parameter for the control resource set to conform to a unified TCI state and the setting does not include the first parameter, the control unit determines the monitoring occasion based on a synchronization signal block referenced by the one TCI state based on the instruction. <Note 3> If the setting does not include a second parameter for the control resource set to conform to a unified TCI state, the control unit determines the monitoring occasion based on a synchronization signal block determined by the most recent of a medium access control (MAC) control element (CE) activation command indicating a single TCI state, a random access procedure, and a setting grant physical uplink shared channel (PUSCH) transmission, as described in Note 1 or Note 2. <Note 4> The single TCI state includes a channel state information (CSI)-reference signal (RS) pseudo-collocated with the synchronization signal block, as described in any of Notes 1 to 3.<Note A> A base station comprising: a transmitting unit that transmits a setting of a control resource set having index 0 and an instruction for one or more transmission configuration indication (TCI) states; and a control unit that, if the one or more TCI states are two TCI states and the setting includes a first parameter for determining one of the two TCI states, determines the monitoring occasion for one or more physical downlink control channel (PDCCH) candidates in a search space having index 0 based on a synchronization signal block referenced by the one TCI state.

[0168] <Supplement> The terminal in Appendix 1 to Appendix 4 may be terminal 20. The receiving / transmitting unit in Appendix 1 to Appendix 4 may be transmitting / receiving unit 220. The control unit in Appendix 1 to Appendix 4 may be control unit 210. The base station in Appendix A may be base station 10. The receiving / transmitting unit in Appendix A may be transmitting / receiving unit 120. The control unit in Appendix A may be control unit 110.

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

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

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

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

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

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

[0175] 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 by multiple antennas / base stations 10. One [virtual] cell (which may be called a supercell, for example) may be composed of multiple [virtual] cells (which may be called subcells, for example). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell whose physical range fluctuates quasi-statically / dynamically. In this case, the wireless communication system 1 may be called a cell-free system.

[0176] Terminal 20 may be connected to at least one of the multiple base stations 10. Terminal 20 may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC).

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

[0178] Furthermore, terminal 20 may communicate in each CC using at least one of time division duplex (TDD) and frequency division duplex (FDD).

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

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

[0181] The core network 30 may include, for example, network functions (Network Functions (NFs)) such as User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Unified Data Management (UDM), Application Function (AF), Data Network (DN), Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM)). Multiple functions may be provided by a single network node (which may simply be called a node). Furthermore, communication with an external network (e.g., the Internet) may occur via the DN.

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

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

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

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

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

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

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

[0189] Furthermore, the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. Furthermore, PDSCH may be read as DL data, and PUSCH may be read as UL data.

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

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

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

[0193] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted from the names of various channels.

[0194] 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, the DL-RS may include 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.

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

[0196] Furthermore, in the wireless communication system 1, the uplink reference signal (UL-RS) may include a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. The DMRS may also be called a user-specific reference signal (UE-specific Reference Signal).

[0197] (Base Station) Figure 4 shows an example of the configuration of a base station according to one embodiment of the present disclosure. The base station 10 includes a control unit 110, a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, the transmitting / receiving unit 120, the transmitting / receiving antenna 130, and the transmission line interface 140 may be provided.

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

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

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

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

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

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

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

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

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

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

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

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

[0210] The transmitting / receiving unit 120 (receiving 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 (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.

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

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

[0213] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0214] 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 implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level physical layer functions (precoding, IFFT, FFT, etc.). The DU may implement higher-level physical layer functions (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.

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

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

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

[0218] In this example, the functional blocks of the characteristic parts of this 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 part described below may be omitted.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0233] The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. 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 interference measurement resources. Interference measurement resources may be at least one of the following: NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. CSI-IM may also be called CSI-Interference Management (IM), and may be interpreted interchangeably with Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., may be interpreted interchangeably.

[0234] In this disclosure, the transmitting unit and receiving unit of the terminal 20 may be composed of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.

[0235] (Hardware Configuration) The block diagram used in the description of the above embodiment shows functional units. These functional blocks (components) are realized by hardware, software, or a combination thereof. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

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

[0237] In this disclosure, any two terms selected from the set of terms such as apparatus, circuit, device, section, unit, module, chip, and means may be read as interchangeable. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

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

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

[0240] Furthermore, the processor 1001 reads programs (program code), 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 accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly.

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

[0242] Furthermore, this disclosure also provides a computer program product, which includes a computer program. This computer program product may implement the steps of the method described in the above embodiments when the computer program is executed by a computer (for example, a processor 1001).

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

[0244] The storage 1003 is a [non-temporary] computer-readable recording medium, which may consist of, for example, a flexible disk, a floppy disk, an optical disk (e.g., Compact Disc ROM (CD-ROM), etc.), a digital multipurpose disk, a Blu-ray disk), a magneto-optical disk, a removable disk, a hard disk drive, a smart card, flash memory (e.g., a card, stick, key drive), a magnetic stripe, or at least two of these. The storage 1003 may also be called an auxiliary storage device.

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

[0246] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via a wired network, a wireless network, or both wired and wireless networks, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, duplexer, filter, frequency synthesizer, or at least two combinations thereof. For example, the above-mentioned transmit / receive unit 120 (220), transmit / receive antenna 130 (230), etc., may be implemented by the communication device 1004. The transmit / receive unit 120 (220) may be implemented in physically or logically separated form, consisting of a transmit unit 120a (220a) and a receive unit 120b (220b).

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

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

[0249] Furthermore, the base station 10 and terminal 20 may be configured with 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 each functional block may be realized using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0250] In this disclosure, the term “processor” may encompass a single processor or a group of processors, including, for example, a single-core processor, a multi-core processor, multiple processors in a single device, or multiple processors that can communicate with each other by wire or wireless means. Similarly, the term “[non-temporary] computer-readable recording medium” may encompass a single storage medium or a group of storage mediums, including multiple storage mediums that can communicate with each other by wire or wireless means.

[0251] The devices in this disclosure, such as processors and storage media, may be distributed locally or remotely, and may perform processing by operating cooperatively or independently using buses, networks, the internet, clouds, etc.

[0252] Furthermore, devices included in the core network 30 (for example, network nodes that provide NF) may also be implemented using the functional block / hardware configuration described above.

[0253] (Modifications) Each aspect / embodiment described in this disclosure is 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 (where x is, for example, an integer or decimal)), 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®), Global System for Mobile communications (GSM®), CDMA2000, Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.11x (where x is any string such as b, a, g, n, ac, ax, be, bn, etc., and x=n is Wi-Fi4, x=ac is Wi-Fi5, x=ax is Wi-Fi6 or Wi-Fi6E, x=be is Wi-Fi7, x=bn is Wi-Fi8, etc.)The invention may also be applied to systems based on technologies such as Wi-Fi (a registered trademark), IEEE 802.16 (WiMAX®), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth®, 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 this disclosure may be applied to systems based on a combination of at least two of these technologies. Hereinafter, "based on" means not only systems that utilize the technologies, but also systems that utilize extensions or modifications of the technologies.

[0254] In this disclosure, the terms "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", "Ground Base Station", "Stratospheric Base Station", "Unmanned Aerial Vehicle", "High Altitude Platform Station (HAPS)", "Airborne Platform", "Panel", "Cell", and "Radio Access Network (Radio Access)" are used. Any two terms selected from the set of terms such as "Network (RAN)" and "Network" may be used interchangeably. Each cell accommodated by a base station may be referred to by terms such as macrocell, small cell, femtocell, picocell, serving cell, or supercell. In this disclosure, any two terms selected from the set of terms such as "cell," "sector," "cell group," "carrier," "component carrier," "cluster," "bandwidth part (BWP)," and "carrier bandwidth" may be used interchangeably.

[0255] In this disclosure, any two terms selected from the set of terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "Device", "module", and "terminal" may be used interchangeably.

[0256] The terminal may be called a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, router (e.g., home router, mobile router, etc.), Telematics Control Unit (TCU), or some other appropriate term.

[0257] A base station and a terminal may each consist of one or more devices. At least some of the devices constituting a base station and a terminal may be called a transmitting device, a receiving device, a wireless communication device, etc. Furthermore, the devices constituting at least a part of each base station and terminal may be, but are not limited to, objects themselves such as vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, 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, and Internet of Things (IoT) devices (e.g., smart meters, sensors), or include, but are not limited to, objects or devices mounted on such objects. Furthermore, the object in question may be a moving object (hereinafter referred to as a "moving object," without prejudice that the moving object may be in a stationary state) or a fixedly positioned object (hereinafter referred to as a "non-moving object").

[0258] Furthermore, the term "base station" in this disclosure may be interpreted as "terminal." For example, the various aspects / embodiments of this disclosure may be applied to configurations 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), Vehicle-to-Everything (V2X), etc.) or communication over a Non-Terrestrial Network (NTN). In this case, the terminal 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink") or terms corresponding to NTN (for example, feeder link, service link). For example, uplink channel, downlink channel, etc., may be interpreted as sidelink channel.

[0259] Furthermore, this disclosure is also applicable when at least some of the equipment constituting the base station and terminal operates outside of the ground (for example, in the atmosphere or in outer space).

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

[0261] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node, or by a part of it (e.g., CU, RU, DU, etc.). It is clear that various operations performed for communication with terminals in a RAN or core network may be performed by at least a part of the base station and other network nodes other than the base station. The other network nodes may be a single node or a combination of multiple nodes. A 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 (NFs).

[0262] Furthermore, in this disclosure, the action of "a terminal receiving information from a base station" is accompanied by the actions of "a base station transmitting the information to the terminal," "a base station generating the information," or both. Similarly, the action of "a terminal transmitting information to a base station" is accompanied by the action of "a base station receiving the information from the terminal." In addition, actions such as "a terminal is configured to..." or "a terminal is configured to..." may include the actions of "a base station transmitting configuration information regarding the terminal's settings" or "the terminal configuring a predetermined action based on the configuration information."

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

[0264] Physical layer signaling may also be called Layer 1 (L1) control information. MAC signaling may be called, for example, a MAC control element (CE), a MAC protocol data unit (PDU), etc. RRC signaling may also be called an RRC message or an information element (IE) within such an RRC message. Such RRC signaling may be a message used for, for example, controlling an RRC connection (e.g., setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, measurement report, terminal capability notification, etc., or it may be an information element within such a message.

[0265] Furthermore, notification of information may be explicit or implicit. Explicit notification of information means notifying the information itself, while implicit notification of information may be notification of other information or the fulfillment of certain conditions which constitutes notification of the information.

[0266] Furthermore, information notification may include not only notifications between the same layer of different devices (for example, between lower layers or upper layers of base station 10 and terminal 20), but also notifications between different layers within the same or different devices (for example, between lower layers and upper layers within base station 10 or terminal 20). Also, information notification from one device to another may be carried out via one or more devices.

[0267] Any information described in this disclosure (e.g., variables, constants, parameters, settings) may be communicated from any first device (e.g., terminal / base station) to any second device (e.g., base station / terminal) to any second device (e.g., base station / terminal) to any first device (e.g., base station / terminal) to any second device (e.g., base station / terminal) to any second device (e.g., base station / terminal) to any second device (e.g., base station / terminal) to any second device (e.g., base station / terminal) to any second device (e.g., base station / terminal) to any second device (e.g., base station / terminal) to any second device (e.g., base station / terminal) to any second device (e.g., base station / base station

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

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

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

[0271] For example, a resource in the time domain (which may also be called a time resource) may be defined by one or more time units. These one or more time units may include, for example, a radio frame, a subframe, a slot, a symbol, and a transmission time interval (TTI), or at least two of these, but the names of the time units are not limited to these. Furthermore, these time units may be fixed-length time units that do not depend on numerology, variable-length time units that depend on numerology, or both.

[0272] Examples of fixed-length time units include, but are not limited to, subframes consisting of one or more slots, and wireless frames containing multiple subframes. Examples of variable-length time units include, but are not limited to, symbols and slots containing a fixed number of symbols. A certain time unit may be divided into shorter time units. Examples of shorter time units include, but are not limited to, mini-slots consisting of fewer symbols than the number of symbols that make up a slot. Such time units may include, for example, time units used as units for scheduling, link adaptation, etc. Furthermore, any time unit in this disclosure may be interpreted as a substitute for another time unit.

[0273] Numerology refers to parameters that define the physical layer structure, and may be parameters based on at least one of the following: subcarrier spacing (SCS), symbol length, cyclic prefix length, and sampling time.

[0274] Resources in the frequency domain (which may also be called frequency resources) may be defined, for example, by one or more frequency units. Such one or more frequency units may include, for example, subcarriers, resource blocks (RBs), bandwidth parts (BWPs), carrier bandwidths, or at least two combinations thereof, but the names of frequency units are not limited to these. Furthermore, the number of subcarriers included in a frequency unit may be a fixed number regardless of the neurology, or it may be a variable number that changes depending on the neurology.

[0275] For example, an RB consists 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 the neurology, and may be, for example, 12, but is not limited thereto. Also, a BWP may consist of, for example, one or more consecutive RBs within a certain carrier bandwidth, but is not limited thereto. One or more BWPs may be set up for a terminal 20 within a single carrier, and at least one of the BWPs may be activated. Furthermore, any frequency unit in this disclosure may be interpreted as any other frequency unit.

[0276] Furthermore, resources in both the time domain and the frequency domain may be defined in one or more time / frequency units, for example, consisting of time units and frequency units. Such time / frequency units are, but are 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.

[0277] Resources in a spatial domain (which may also be called spatial resources) may be defined, for example, by one or more spatial units. Such one or more spatial units include, but are not limited to, beams, Multi Input Multi Output (MIMO) layers, antenna ports, or at least two combinations thereof.

[0278] Resources in the code domain (which may also be called code resources) may be defined, for example, by one or more code units. These one or more code units include, but are not limited to, cyclic shifts (CS), orthogonal cover codes (OCC), or combinations thereof.

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

[0280] In this disclosure, the words "decide," "determine," "judge," "select," "specify," "compute," "calculate," "process," "derive," "look up / search / inquiry," "confirm," "assume," "expect," and "consider" may be interpreted interchangeably. Also, in this disclosure, performing a certain process (e.g., sending, receiving) may be interpreted interchangeably with deciding to perform that process. Furthermore, in this disclosure, "do not assume that..." may be interpreted interchangeably with "assume that..."

[0281] In this disclosure, "expect" may be rephrased as "be expected." For example, "expect(s) ..." (where "..." may be expressed as a that clause, an infinitive, etc.) may be rephrased as "be expected ..." or "do (the verb without "to" if "..." is an infinitive)." Similarly, "does not expect ..." may be rephrased as "be not expected ..." or "do not (the verb without "to" if "..." is an infinitive)." Furthermore, "An apparatus A is not expected ..." may be rephrased 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).

[0282] In this disclosure, "less than or equal to," "less than," "greater than or equal to," "more than," and "equal to" may be interpreted interchangeably. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees, by adding "i-th" (where i is any integer) to the expression (for example, "highest" may be interpreted interchangeably with "i-th highest").

[0283] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.

[0284] In this disclosure, phrases 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. Furthermore, A, B, etc., may be replaced with appropriate expressions such as nouns, gerunds, or regular sentences depending on the context. The time difference between A and B may be approximately zero (immediately after or immediately before). Additionally, a time offset may be applied to the time when A occurs. For example, "A" may be interpreted as "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predetermined or determined by the UE based on notified information.

[0285] In this disclosure, timing, time, duration, time instance, any unit of time (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc., may be interpreted interchangeably.

[0286] In this 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,” and “receiving entity” may be used interchangeably.

[0287] In this disclosure, "antenna port" may be interpreted interchangeably with "antenna port for any signal / channel (e.g., a DeModulation Reference Signal (DMRS) port)." In this disclosure, "resource" may be interpreted interchangeably with "resource for any signal / channel (e.g., a reference signal resource)." Furthermore, a spatial domain filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0288] In this disclosure, beam, sounding reference signal (SRS), resource indicator (SRS Resource Indicator (SRI)), control resource set (CORESET), CORESET pool, physical downlink shared channel (PDSCH), physical uplink shared channel (PUSCH), codeword (CW), transport block (TB), reference signal (RS) and the like may be interchangeable.

[0289] In this disclosure, TCI state, TCI, Downlink (DL) TCI state, Uplink (UL) TCI state, unified TCI state, common TCI state, joint TCI state, etc., may be interpreted interchangeably.

[0290] Furthermore, in this disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interpreted interchangeably.

[0291] In this disclosure, the terms index, identifier (ID), identity (ID), indicator, indication, resource ID, etc., may be interpreted interchangeably. In this disclosure, the terms sequence, list, set, group, cluster, subset, etc., may be interpreted interchangeably.

[0292] In this disclosure, the group may include, for example, at least one of the following: 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, or a panel group.

[0293] The information in this disclosure (e.g., variables, constants, parameters, settings) may be interpreted as IDs of such information. For example, TCI status and TCI status ID may be interpreted as IDs of such information. In addition, the information in this disclosure may be interpreted as "a set of such information," "one or more such pieces of information," etc.

[0294] Any signal / channel in this disclosure (e.g., PUCCH) may be interpreted as another signal / channel (e.g., PUSCH, PDSCH, any RS). A signal / channel may be interpreted as a signal / channel for the same direction (e.g., if the above signal / channel is in the UL direction, it is UL, and if it is in the DL direction, it is DL), or as a signal / channel for the opposite direction (e.g., if the above signal / channel is in the UL direction, it is DL, and if it is in the DL direction, it is UL). Also, in this disclosure, descriptions relating to DL communication and descriptions relating to UL communication may be interpreted as one another. In this case, the operation of DL (UL) may be interpreted as the operation of the corresponding UL (DL). For example, the reception of PDSCH at a terminal may be interpreted as the transmission of PUSCH at the same terminal.

[0295] In this disclosure, "X's number," "X number," "the number of X(s)," and "a number of X(s)" may be interpreted as interchangeable. Herein, X may be replaced with a noun, gerund, or ordinary sentence as appropriate, depending on the context. In this disclosure, "number" may be interpreted as maximum number, minimum number, average number, total number, etc. Furthermore, in this disclosure, terms related to "value," "index," "number," and "quantity" may be interpreted as interchangeable.

[0296] Values / ranges in this disclosure may be interpreted as approximations, as if preceded by the words “about” or “near.” In this disclosure, “[A and B] [are] the same” (where 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 [partly] overlapped),” or “[There is] an error within a certain range [between A and B]” (i.e., these words may be interpreted as interchangeable). Furthermore, in this disclosure, "A and B are the same" may mean that at least part of A and at least part of B are the same (or overlapped).

[0297] In this disclosure, “one embodiment,” “several embodiments,” and “another embodiment” may be used interchangeably. In this disclosure, the terms “one embodiment,” “several embodiments,” and “another embodiment” do not necessarily all refer to the same embodiment, nor do they necessarily mean that they are mutually exclusive.

[0298] In this 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 interpreted as including “only A,” “only B,” or “both A and B.” Furthermore, in this disclosure, expressions such as “at least one of A, B or C,” “at least one of A, B or C,” “A, B and / or C,” and “A / B / C” may be interpreted as including “only A,” “only B,” “only C,” “A and B,” “B and C,” “C and A,” or “all of A, B and C.” Similar reinterpretations may be applied to any expression in this disclosure that means "at least X of ..." (where the number of elements in "..." and X are arbitrary numbers).

[0299] In this 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 interpreted as one another.

[0300] In this disclosure, expressions representing one / singular X (e.g., "a X," "one X," "a single X"), expressions representing one or more X (e.g., "one or more X(s)," "at least one of X(s)"), and expressions representing multiple X (e.g., "Xs," "more than one X(s)," "multiple X(s)," "a plurality of X(s)") may be interpreted as one another. These expressions may also be interpreted as one another with expressions that include specific wording (e.g., "pieces of," "amount of," etc., when X is an uncountable noun). For example, "a plurality of pieces of spatial relation information" may be interpreted as "a plurality of spatial relation information."

[0301] The above description of the disclosure is illustrative, and the present invention is not limited to the embodiments described herein. The disclosure can be implemented as modified and altered forms without departing from the spirit of the invention. The disclosure and its modifications and altered forms are included within the scope of the present invention and its equivalents.

[0302] This application is based on Japanese Patent Application No. 2025-081543, filed on 14 May 2025. All of its contents are included herein.

Claims

1. A terminal having a receiving unit that receives a setting of a control resource set having index 0 and an instruction for one or more transmission configuration indication (TCI) states, and a control unit that, if the one or more TCI states are two TCI states and the setting includes a first parameter for determining one of the two TCI states, determines the monitoring occasion for one or more physical downlink control channel (PDCCH) candidates in a search space having index 0 based on a synchronization signal block referenced by the one TCI state.

2. The terminal according to claim 1, wherein if the setting includes a second parameter for the control resource set to conform to a unified TCI state, and the setting does not include the first parameter, the control unit determines the monitoring occasion based on a synchronization signal block referenced by a single TCI state based on the instruction.

3. If the setting does not include a second parameter for the control resource set to conform to a unified TCI state, the control unit determines the monitoring occasion based on a synchronization signal block determined by the most recent of a medium access control (MAC) control element (CE) activation command indicating a single TCI state, a random access procedure, and a setting grant physical uplink shared channel (PUSCH) transmission, according to claim 1.

4. The terminal according to claim 1, wherein one TCI state includes a channel state information (CSI)-reference signal (RS) that is pseudo-collated with the synchronization signal block.

5. A wireless communication method for a terminal, comprising: receiving a setting of a control resource set having index 0; receiving an instruction for one or more transmission configuration indication (TCI) states; and, if the one or more TCI states are two TCI states and the setting includes a first parameter for determining one of the two TCI states, determining the monitoring occasion for one or more candidate physical downlink control channels (PDCCH) in a search space having index 0 based on a synchronization signal block referenced by the one TCI state.

6. A base station having: a transmitting unit that transmits a control resource set setting having index 0 and an instruction for one or more transmission configuration indication (TCI) states; and a control unit that, if the one or more TCI states are two TCI states and the setting includes a first parameter for determining one of the two TCI states, determines the monitoring occasion for one or more physical downlink control channel (PDCCH) candidates in a search space having index 0 based on a synchronization signal block referenced by the one TCI state.