WO2024181346A1

WO2024181346A1 - Terminal, wireless communication method, and base station

Info

Publication number: WO2024181346A1
Application number: PCT/JP2024/006752
Authority: WO
Inventors: 祐輝松村; 聡永田
Original assignee: 株式会社Ｎｔｔドコモ
Priority date: 2023-02-28
Filing date: 2024-02-26
Publication date: 2024-09-06

Abstract

A terminal according to one embodiment of the present disclosure comprises: a control unit that, when the offset between the reception of downlink control information for scheduling a downlink signal and the reception of the downlink signal is less than a specified threshold, controls buffers of the downlink signal using one or more indicated transmission configuration indication (TCI) states, on the basis of a report of capability information relating to the number of buffers of the downlink signal and/or a configuration relating to the number of buffers; and a reception unit that performs processing for receiving the downlink signal by using the one or more indicated TCI states. According to the one embodiment of the present disclosure, TCI states can be appropriately applied.

Description

Terminal, wireless communication method and base station

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

Long Term Evolution (LTE) was specified for Universal Mobile Telecommunications System (UMTS) networks with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). In addition, LTE-Advanced (3GPP Rel. 10-14) was specified for the purpose of achieving higher capacity and greater sophistication over LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later, etc.) are also under consideration.

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

　Applying the set/activated/indicated TCI state to multiple types of signals (channels/RS) is being considered. However, there are cases where the method for indicating the TCI state is not clear. If the method for indicating the TCI state is not clear, this may lead to a deterioration in communication quality, a decrease in throughput, etc.

Therefore, one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that appropriately applies the TCI state.

A terminal according to one aspect of the present disclosure has a control unit that controls the buffer of the downlink signal using one or more command transmission configuration indication (TCI) states based on at least one of a report of capability information regarding the number of buffers for the downlink signal and a setting regarding the number of buffers when an offset between the reception of downlink control information that schedules a downlink signal and the reception of the downlink signal is smaller than a specific threshold value, and a receiving unit that performs reception processing of the downlink signal using the one or more command TCI states.

According to one aspect of the present disclosure, the TCI state can be appropriately applied.

1A and 1B show an example of a unified/common TCI framework. 2A and 2B show an example of DCI-based TCI status indication. FIG. 3 shows an example of application times for the Unified TCI Status Indication. 4A to 4D are diagrams showing an example of a multi-TRP. 5A-5C are diagrams illustrating an example of application of an indicated TCI state. 6A-6C are diagrams illustrating another example of application of an indicated TCI state. 7A to 7D are diagrams showing an example of application of an indicated TCI state according to embodiment 1-1. 8A to 8D are diagrams showing an example of application of an indicated TCI state according to embodiment 1-2. FIG. 9 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 10 is a diagram illustrating an example of the configuration of a base station according to an embodiment. FIG. 11 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. FIG. 12 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. FIG. 13 is a diagram illustrating an example of a vehicle according to an embodiment.

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

The TCI state may represent that which applies to the downlink signal/channel. The equivalent of the TCI state which applies to the uplink signal/channel may be expressed as a spatial relation.

TCI state is information about the Quasi-Co-Location (QCL) of signals/channels and may also be called spatial reception parameters, spatial relation information, etc. TCI state may be set in the UE on a per channel or per signal basis.

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

The spatial reception parameters may correspond to a reception beam (e.g., a reception analog beam) of the UE, and the beam may be identified based on a spatial QCL. The QCL (or at least one element of the QCL) in this disclosure may be interpreted as sQCL (spatial QCL).

Multiple types of QCLs (QCL types) may be defined. For example, four QCL types A-D may be provided, each of which has different parameters (or parameter sets) that can be assumed to be the same.

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

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

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

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

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

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

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

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

[Physical Layer Procedures for Data/Antenna Port QCL]
A UE can configure a list of up to M TCI-State settings in the higher layer parameter PDSCH-Config for decoding of PDSCH according to a detected PDCCH with DCI intended for the UE and a given serving cell, where M depends on the UE capability maxNumberConfiguredTCIstatesPerCC.

Each TCI-State includes parameters for setting the QCL relationship between one or two downlink reference signals and the DMRS port of the PDSCH, the DMRS port of the PDCCH, or the CSI-RS port of the CSI-RS resource. The QCL relationship is set by the higher layer parameters qcl-Type1 for the first DL RS and qcl-Type2 for the second DL RS (if configured).

In the case of two DL RSs, the multiple QCL types are not the same, regardless of whether the references are to the same DL RS or to different DL RSs. The QCL type corresponding to each DL RS is given by the higher layer parameter qcl-Type in QCL-Info and can take one of the following values:
- 'typeA': {Doppler shift, Doppler spread, average delay, delay spread}
- 'typeB': {Doppler shift, Doppler spread}
- 'typeC': {Doppler shift, average delay}
- 'typeD': {Spatial Rx parameter}

[RRC Protocol Specifications/RRC IE/TCI States]
A TCI-State associates one or two DL Reference Signals (RS) with a corresponding QCL type. If an additional physical cell identifier (PCI) is configured for that RS, it is set to the same value for both DL RSs.

(Default TCI State/Default Spatial Relationship/Default PL-RS)
In Rel. 16, the PDSCH may be scheduled in a DCI having a TCI field. The TCI state for the PDSCH is indicated by the TCI field. The TCI field of DCI format 1_1 is 3 bits, and the TCI field of DCI format 1_2 is up to 3 bits.

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

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

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

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

In Rel. 15, separate MAC CEs are required for activation/deactivation of the PUCCH spatial relationship and for activation/deactivation of the SRS spatial relationship. The PUSCH spatial relationship follows the SRS spatial relationship.

In Rel. 16, at least one of the MAC CE for activation/deactivation of the PUCCH spatial relationship and the MAC CE for activation/deactivation of the SRS spatial relationship may not be used.

If neither the spatial relationship nor the PL-RS for the PUCCH is configured in FR2 (applicable condition, second condition), the default assumptions of the spatial relationship and the PL-RS for the PUCCH (default spatial relationship and default PL-RS) are applied. If neither the spatial relationship nor the PL-RS for the SRS (SRS resource for the SRS, or SRS resource corresponding to the SRI in DCI format 0_1 that schedules the PUSCH) is configured in FR2 (applicable condition, second condition), the default assumptions of the spatial relationship and the PL-RS for the PUSCH and the SRS scheduled by DCI format 0_1 (default spatial relationship and default PL-RS) are applied.

If a CORESET is configured in the active DL BWP on that CC (applicable condition), the default spatial relationship and default PL-RS may be the TCI state or QCL assumption of the CORESET with the lowest CORESET ID in that active DL BWP. If a CORESET is not configured in the active DL BWP on that CC, the default spatial relationship and default PL-RS may be the active TCI state with the lowest ID of the PDSCH in that active DL BWP.

In Rel. 15, the spatial relationship of PUCCH scheduled by DCI format 0_0 follows the spatial relationship of the PUCCH resource with the lowest PUCCH resource ID among the active spatial relationships of PUCCH on the same CC. The network needs to update the PUCCH spatial relationship on all SCells even if no PUCCH is transmitted on the SCell.

In Rel. 16, PUCCH configuration is not required for a PUSCH scheduled by DCI format 0_0. If there is no active PUCCH spatial relationship or no PUCCH resources on the active UL BWP in a CC for a PUSCH scheduled by DCI format 0_0 (applicable condition, second condition), the default spatial relationship and default PL-RS are applied to the PUSCH.

The conditions for applying the default spatial relationship/default PL-RS for SRS may include setting the default beam path loss enable information element for SRS (upper layer parameter enableDefaultBeamPlForSRS) to be enabled. The conditions for applying the default spatial relationship/default PL-RS for PUCCH may include setting the default beam path loss enable information element for PUCCH (upper layer parameter enableDefaultBeamPlForPUCCH) to be enabled. The conditions for applying the default spatial relationship/default PL-RS for PUSCH scheduled by DCI format 0_0 may include setting the default beam path loss enable information element for PUSCH scheduled by DCI format 0_0 (upper layer parameter enableDefaultBeamPlForPUSCH0_0) to be enabled.

In Rel. 16, if the RRC parameters (parameter to enable the default beam PL for PUCCH (enableDefaultBeamPL-ForPUCCH), parameter to enable the default beam PL for PUSCH (enableDefaultBeamPL-ForPUSCH0_0), or parameter to enable the default beam PL for SRS (enableDefaultBeamPL-ForSRS)) are configured for the UE and the spatial relationship or PL-RS is not configured, the UE applies the default spatial relationship/PL-RS.

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

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

The default TCI state for PDSCH in Rel. 15/16 is specified as a default TCI state for a single TRP, a default TCI state for multiple TRPs based on multiple DCIs, and a default TCI state for multiple TRPs based on a single DCI.

In Rel. 15/16, the default TCI state for aperiodic CSI-RS (A (aperiodic)-CSI-RS) is specified as follows: default TCI state for single TRP, default TCI state for multi-TRP based on multi-DCI, and default TCI state for multi-TRP based on single DCI.

In Rel. 15/16, the default spatial relationship and default PL-RS for each of PUSCH/PUCCH/SRS are specified.

(Unified/Common TCI Framework)
According to the unified TCI framework, multiple types of (UL/DL) channels/RSs can be controlled by a common framework. The unified TCI framework does not specify the TCI state or spatial relationship for each channel as in Rel. 15, but instead specifies a common beam (common TCI state) and may apply it to all UL and DL channels, or a common beam for UL may apply to all UL channels and a common beam for DL may apply to all DL channels.

One common beam for both DL and UL, or one common beam for DL and one common beam for UL (total of two common beams) are being considered.

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

The UL and DL default beams may be aligned via MAC CE based beam management (MAC CE level beam instructions). The PDSCH default TCI state may be updated to match the default UL beam (spatial relationship).

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

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

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

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

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

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

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

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

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

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

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

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

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

In addition, in this disclosure, the higher layer parameters (RRC parameters) that set multiple TCI states may be referred to as configuration information that sets multiple TCI states, or simply as "configuration information." Also, in this disclosure, being instructed to set one of multiple TCI states using DCI may mean receiving indication information that indicates one of the multiple TCI states included in DCI, or may simply mean receiving "instruction information."

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

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

In Rel. 17 NR and later, it is assumed that the MAC CE/DCI will support beam activation/indication to a TCI state associated with a different physical cell identifier (PCI). Also, in Rel. 18 NR and later, it is assumed that the MAC CE/DCI will support indicative serving cell change to a cell with a different PCI.

[Physical Layer Procedures for Data/Antenna Port QCL]
In order to provide a reference signal for PDSCH DMRS and PDCCH DMRS, CSI-RS in a CC, and further to provide a reference for UL TX (transmission) spatial filter determination for dynamic grant and configuration grant based PUSCH and PUCCH resources, SRS in a CC, if such a filter is available, the UE can configure a list of up to 128 DLorJointTCIState configurations in PDSCH-Config.

If there is no DLorJointTCIState or UL-TCIState setting in the BWP in that CC, the UE may apply the DLorJointTCIState or UL-TCIState setting from the reference BWP of the reference CC. If the UE has DLorJointTCIState or UL-TCIState set in any CC in the same band, it does not assume that TCI-State, SpatialRelationInfo (spatial relation information), or PUCCH-SpatialRelationInfo (PUCCH spatial relation information) in that band are set, except for SpatialRelationInfoPos (spatial relation information for position). The UE assumes that if the UE has TCI-State in any CC in the CC list configured by simultaneousTCI-UpdateList1-r16, simultaneousTCI-UpdateList2-r16, simultaneousSpatial-UpdatedList1-r16, or simultaneousSpatial-UpdatedList2-r16, the UE does not configure DLorJointTCIState or UL-TCIState in any CC in the CC list.

The UE receives an activation command that is used to map up to eight TCI states and/or TCI state pairs, with one TCI state for DL channels/signals and one TCI state for UL channels/signals, to code points of the DCI field 'Transmission Configuration Indication' (TCI) for one of the CC/DL BWPs or for a set of CC/DL BWPs, if available. If a set of TCI state IDs is activated for a set of CC/DL BWPs and, if available, for one of the CC/DL BWPs, the same set of TCI state IDs applies to all DL and/or UL BWPs in the indicated CC, where the applicable list of CCs is determined by the CCs indicated in the activation command. If the activation command maps DLorJointTCIState and/or UL-TCIState to only one TCI code point, the UE applies the indicated DLorJointTCIState and/or UL-TCIState to one or a set of CC/DL BWPs, and if the indicated mapping to a single TCI code point applies, the UE applies the indicated DLorJointTCIState and/or UL-TCIState to one or a set of CC/DL BWPs.

If the bwp-id or cell for a QCL type A/D source RS in the QCL-Info of a TCI state with DLorJointTCIState set is not set, the UE shall assume that the QCL type A/D source RS is set in the CC/DL BWP to which the TCI state applies.

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

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

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

Note that the DCI in the above Mode 2/Mode 3 may be called beam instruction DCI.

In Rel. 15/16, if the UE does not support active BWP change via DCI, the UE will ignore the BWP indicator field. A similar behavior is considered for the relationship between Rel. 17 TCI state support and the interpretation of the TCI field. If the UE is configured with Rel. 17 TCI state, the TCI field will always be present in DCI format 1_1/1_2, and if the UE does not support TCI update via DCI, the UE will ignore the TCI field.

In Rel. 15/16, the presence or absence of a TCI field (TCI presence information in DCI, tci-PresentInDCI) is set for each CORESET.

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

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

Figure 2A shows an example of a DCI-based joint DL/UL TCI status indication. A TCI status ID indicating the joint DL/UL TCI status is associated with the value of the TCI field for the joint DL/UL TCI status indication.

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

(Indicated TCI Status/Set TCI Status)
For Rel. 17 TCI states, the unified/common TCI state may mean the Rel. 17 TCI state indicated using (Rel. 17) DCI/MAC CE/RRC (indicated Rel. 17 TCI state).

In this disclosure, the terms indicated Rel. 17 TCI state, indicated TCI state, unified/common TCI state, TCI state applicable to multiple types of signals (channels/RS), and TCI state for multiple types of signals (channels/RS) may be interpreted interchangeably.

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

With respect to the Rel. 17 TCI state, a TCI state other than the unified TCI state may refer to a Rel. 17 TCI state configured using the (Rel. 17) MAC CE/RRC (configured Rel. 17 TCI state). In this disclosure, the configured Rel. 17 TCI state, the configured TCI state, a TCI state other than the unified TCI state, and a TCI state applied to a specific type of signal (channel/RS) may be read as interchangeable.

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

It is being considered that the indicated Rel. 17 TCI state will be applied to UE-specific channels/signals (RS). It is also being considered that the UE will be notified using higher layer signaling (RRC signaling) as to whether the indicated Rel. 17 TCI state or the configured Rel. 17 TCI state will be applied to non-UE-specific channels/signals.

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

It is being considered that the UE will update the indicated TCI state and the configured TCI state separately. For example, if the unified TCI state for the indicated TCI state is updated for the UE, the configured TCI state may not need to be updated. It is also being considered that the UE will make a decision about the update based on a specific parameter.

In addition, it is being considered to use higher layer signaling (RRC/MAC CE) to switch between whether the indicated Rel. 17 TCI state is applied to the PDCCH/PDSCH or not (the configured Rel. 17 TCI state is applied, or a TCI state configured separately from the indicated Rel. 17 TCI state is applied).

In addition, for intra-cell beam indication (TCI state indication), it is being considered to support Rel. 17 TCI state indication for UE-specific CORESET and PDSCH associated with that CORESET, and non-UE-specific CORESET and PDSCH associated with that CORESET.

In addition, for inter-cell beam indication (e.g., L1/L2 inter-cell mobility), support for indication Rel. 17 TCI states for UE-specific CORESETs and their associated PDSCHs is under consideration.

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

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

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

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

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

For non-UE-dedicated channels/RS (excluding CORESET), RRC parameters may be configured for each channel/resource/resource set to follow or not follow the indicated Rel. 17 TCI state. If the indicated Rel. 17 TCI state is not configured for that channel/resource/resource set, the configured Rel. 17 TCI state may be applied to that channel/resource/resource set.

(Channel/RS to which the indicated TCI state applies)
The indicated TCI state by the MAC CE/DCI may apply to the following channels/RS:

[PDCCH]
If followUnifiedTCIState is set for CORESET0, the indicated TCI state is applied. Otherwise, the Rel. 15 specifications are applied for that CORESET. That is, CORESET0 follows the TCI state activated by the MAC CE or is QCLed with SSB.
For a CORESET with index other than 0 with USS/CSS type 3, the indicated TCI state always applies.
- For a CORESET with index other than 0, with at least a CSS other than CSS type 3, configured to follow the uniform TCI state, the indicated TCI state applies. Otherwise, the configured TCI state for that CORESET applies to that CORESET.

[PDSCH]
- The indicated TCI state always applies for all UE-dedicated PDSCHs.
For a non-UE-dedicated PDSCH (PDSCH scheduled by a DCI in the CSS), if followUnifiedTCIState is set (for the CORESET of the PDCCH that schedules the PDSCH), the indicated TCI state may apply. Otherwise, the configured TCI state for the PDSCH applies to the PDSCH. If followUnifiedTCIState is not set for a PDSCH, whether a non-UE-dedicated PDSCH follows the indicated TCI state may depend on whether followUnifiedTCIState is set for the CORESET used to schedule the PDSCH.

[CSI-RS]
For an A-CSI-RS for CSI acquisition or beam management, if followUnifiedTCIState is set (for the CORESET of the PDCCH that triggers that A-CSI-RS), the indicated TCI state applies. For other CSI-RSs, the configured TCI state for that CSI-RS applies.

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

[PUSH]
For dynamic/configured grant PUSCH, the indicated TCI state is always applied.

[SRS]
If the SRS resource set for the A-SRS for beam management and the A/SP/P-SRS for codebook (CB)/non-codebook (NCB)/antenna switching is configured to follow the unified TCI state, the indicated TCI state is applied. For other SRS, the configured TCI state in the SRS resource set is applied.

(beam application time (BAT))
Regarding the DCI-based beam indication in Rel. 17, the following

studies

1 and 2 are being considered regarding the application time of the indication of the beam/unified TCI state (beam application time (BAT) conditions). .

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

In the example of FIG. 3, the ACK may be an ACK for a PDSCH scheduled by the beam instruction DCI. In this example, the PDSCH may not be transmitted. In this case, the ACK may be an ACK for the beam instruction DCI.

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

If the SCS is different between multiple CCs, the value of the Y symbol will also be different, so the application time may differ between multiple CCs.

[Study 2]
For the CA case, the application timing/BAT of the beam instruction may follow any of the following options 1 to 3.
[Option 1] Both the first slot and the Y symbol are determined on the carrier with the smallest SCS among the one or more carriers to which the beam direction applies.
[Option 2] Both the first slot and the Y symbol are determined on the carrier with the smallest SCS among the one or more carriers to which the beam direction applies and the UL carrier carrying the ACK.
[Option 3] Both the first slot and the Y symbol are determined on the UL carrier that carries the ACK.

As part of the CC simultaneous beam update function in Rel. 17, it is being considered to standardize beams between multiple CCs in CA. According to Study 2, the application time will be the same between multiple CCs.

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

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

X [ms] may be used instead of Y [symbol].

Regarding application time, it is considered that the UE reports at least one of the following

UE capabilities

1 and 2.
[UE Capability 1]
Minimum application time per SCS (minimum of Y symbols between the last symbol of the PUCCH carrying ACK and the first slot in which the beam is applied).
UE Capability 2
Minimum time gap between the last symbol of the beam instruction PDCCH (DCI) and the first slot where the beam is applied. The gap between the last symbol of the beam instruction PDCCH (DCI) and the first slot where the beam is applied may meet the UE capability (minimum time gap).

UE capability 2 may be an existing UE capability (e.g., timeDurationForQCL).

The relationship between the beam instruction and the channel/RS to which the beam is applied may satisfy at least one of

UE capabilities

1 and 2.

The parameters set by the base station regarding the application time (e.g., BeamAppTime_r17) may be optional fields.

(Multi-TRP)
In NR, one or more transmission/reception points (TRPs) (multi-TRPs) are considered to perform DL transmission to a UE using one or more panels (multi-panels). It is also considered that a UE performs UL transmission to one or more TRPs.

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

Figures 4A-4D show examples of multi-TRP scenarios. In these examples, we assume that each TRP is capable of transmitting four different beams, but this is not limited to this example.

Figure 4A shows an example of a case where only one TRP (TRP1 in this example) of the multi-TRP transmits to the UE (which may be called single mode, single TRP, etc.). In this case, TRP1 transmits both a control signal (PDCCH) and a data signal (PDSCH) to the UE.

In this disclosure, single TRP mode may refer to the mode when multi-TRP (mode) is not set.

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

Figure 4C shows an example of a case where each of the multi-TRPs transmits a part of a control signal to the UE, and the multi-TRP transmits a data signal (which may be called a master-slave mode). TRP1 may transmit part 1 of the control signal (DCI), and TRP2 may transmit part 2 of the control signal (DCI). Part 2 of the control signal may depend on part 1. The UE receives each PDSCH transmitted from the multi-TRP based on these parts of DCI.

Figure 4D shows an example of a case where each of the multi-TRPs transmits a separate control signal to the UE, and the multi-TRP transmits a data signal (which may be called a multi-master mode). A first control signal (DCI) may be transmitted from TRP1, and a second control signal (DCI) may be transmitted from TRP2. The UE receives each PDSCH transmitted from the multi-TRP based on these DCIs.

When multiple PDSCHs from a multi-TRP such as that shown in FIG. 4B (which may also be called multiple PDSCHs) are scheduled using one DCI, the DCI may be called a single DCI (S-DCI, single PDCCH). Also, when multiple PDSCHs from a multi-TRP such as that shown in FIG. 4D are scheduled using multiple DCIs, these multiple DCIs may be called multiple DCIs (M-DCI, multiple PDCCHs).

Each TRP in a multi-TRP may transmit a different Transport Block (TB)/Code Word (CW)/different layer. Alternatively, each TRP in a multi-TRP may transmit the same TB/CW/layer.

Non-Coherent Joint Transmission (NCJT) is being considered as one form of multi-TRP transmission. In NCJT, for example, TRP1 modulates and maps a first codeword, and transmits a first PDSCH using a first number of layers (e.g., two layers) and a first precoding by layer mapping. TRP2 modulates and maps a second codeword, and transmits a second PDSCH using a second number of layers (e.g., two layers) and a second precoding by layer mapping.

Note that multiple PDSCHs (multi-PDSCHs) that are NCJTed may be defined as partially or completely overlapping with respect to at least one of the time and frequency domains. In other words, the first PDSCH from the first TRP and the second PDSCH from the second TRP may overlap with each other in at least one of the time and frequency resources.

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

In URLLC for multi-TRP, it is considered that PDSCH (transport block (TB) or codeword (CW)) repetition across multi-TRP is supported. It is considered that repetition methods (URLLC schemes, e.g.,

schemes

1, 2a, 2b, 3, 4) across multi-TRP in the frequency domain, layer (spatial) domain, or time domain are supported. In scheme 1, multi-PDSCH from multi-TRP is space division multiplexed (SDM). In schemes 2a and 2b, PDSCH from multi-TRP is frequency division multiplexed (FDM). In scheme 2a, the redundancy version (RV) is the same for multi-TRP. In scheme 2b, the RV may be the same or different for multi-TRP. In

schemes

3 and 4, multiple PDSCHs from multiple TRPs are time division multiplexed (TDM). In scheme 3, multiple PDSCHs from multiple TRPs are transmitted in one slot. In scheme 4, multiple PDSCHs from multiple TRPs are transmitted in different slots.

Such a multi-TRP scenario allows for more flexible transmission control using channels with better quality.

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

For single PDCCH design (mainly for ideal backhaul), TCI extension is being considered. Each TCI code point in the DCI may correspond to

TCI state

1 or 2. The TCI field size may be the same as that of Rel. 15.

For PDCCH/CORESET as specified in Rel. 15, one TCI state without CORESETPoolIndex (also called TRP Info) is set for one CORESET.

With regard to the enhancement of PDCCH/CORESET defined in Rel. 16, in the case of multi-TRP based on multi-DCI, a CORESET pool index is set for each CORESET.

(analysis)
Incidentally, in Rel. 18 and later, the introduction of a case in which multiple TRPs are set and a unified TCI state is applied is being considered.

In multi-TRP operation under existing specifications (up to Rel. 16), the DCI (which may be called a scheduling DCI) that schedules a channel (e.g., PDSCH) controls the number of TCI states that apply to that scheduled channel.

Specifically, if the DCI indicates one TCI state, the UE determines to use a single TRP, and if the DCI indicates two TCI states, the UE determines to use a multi-TRP. In this way, the UE switches between single TRP and multi-TRP based on the number of TCI states indicated by the DCI.

On the other hand, in cases where a multi-TRP is configured in Rel. 18 or later and a unified TCI state is applied, it is being considered that the TCI state indicated by the beam indication DCI will be applied starting after the BAT has elapsed since the transmission of the HARQ-ACK related to that DCI.

For this reason, if switching between single TRP and multi-TRP is performed based on the number of TCI states indicated (indicated TCI states), it is considered that switching by scheduling DCI as in the existing specifications would not be possible.

Specifically, up to X TCI states (indicated TCI states/unified TCI states) (X is an integer equal to or greater than 2 (e.g., 2 or 4)) are indicated to the UE by the RRC/MAC CE/DCI, and then one or more (e.g., two) TCIs are selected/determined from the X TCI states by the scheduling DCI.

In Rel. 18 and later, where such cases are possible, the UE cannot know how many TCI states have been indicated until the DCI decoding is complete.

Figures 5A-5C are diagrams showing an example of application of indicated TCI states. As shown in the example of Figure 5A, four indicated TCI states (TCI#1 as the first TCI state, TCI#2 as the second TCI state, TCI#3 as the third TCI state, and TCI#4 as the fourth TCI state) are indicated to the UE by the RRC/MAC CE/DCI.

As shown in the example of FIG. 5B, switching between single-TRP and multi-TRP is performed by a specific field (existing field (e.g., which may be a TCI field)/new field) included in the scheduling DCI (DCI format 1_1/1_2). In the example shown in FIG. 5B, "00" is indicated as the code point of the field, indicating that the first TCI state is applied (i.e., single-TRP operation is indicated).

Figure 5C shows an example of a UE receiving a scheduling DCI and a scheduled PDSCH, and transmitting a PUCCH corresponding to the PDSCH. The DCI indicates that the first TCI state should be applied, as shown in Figure 5B. At this time, the UE determines that the first TCI state (indicated TCI state, joint/DL TCI state) should be applied to the PDSCH.

The application of the TCI state as shown in Figures 5A-5C is possible if the PDSCH is received after the decoding of the scheduling DCI is completed. If this is not the case (e.g., if the scheduling offset is smaller than a certain threshold), the UE cannot determine the indicated TCI state to apply to the channel/signal (in this case, the PDSCH).

In addition, in Rel. 18 and later, it is being considered that the UE will buffer DL signals using one or more indicated TCI states. In this case, there has been insufficient consideration given to how many/which indicated TCI states the UE should use for buffering.

As such, if sufficient consideration is not given to cases in which the UE cannot determine the TCI state to apply, the TCI state cannot be applied appropriately, which may result in deterioration of communication quality, decrease in throughput, etc.

The inventors therefore came up with a method for appropriately performing operations related to the unified TCI state.

Below, embodiments of the present disclosure will be described in detail with reference to the drawings. The wireless communication methods according to the embodiments may be applied independently or in combination.

In this disclosure, "A/B" and "at least one of A and B" may be interpreted as interchangeable. Also, in this disclosure, "A/B/C" may mean "at least one of A, B, and C."

In this disclosure, terms such as notify, activate, deactivate, indicate, select, configure, update, and determine may be read as interchangeable. In this disclosure, terms such as support, control, capable of control, operate, and capable of operating may be read as interchangeable.

In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In this disclosure, Medium Access Control (MAC Control Element (CE)), update commands, activation/deactivation commands, etc. may be interchangeable.

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

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

In the present disclosure, the physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), etc.

In this disclosure, multi (multiple) TRP, multi TRP system, multi TRP transmission, and multi PDSCH may be interpreted as interchangeable.

In the present disclosure, a single DCI, a single PDCCH, multiple TRP based on a single DCI, activating two TCI states on at least one TCI code point, mapping at least one code point of a TCI field to two TCI states, and setting a specific index (e.g., a TRP index, a CORESET pool index, or an index corresponding to a TRP) for a specific channel/CORESET may be interpreted as interchangeable.

In this disclosure, a single TRP, a channel/signal using a single TRP, a channel using one TCI state/spatial relationship, multi-TRP not being enabled by RRC/DCI, multiple TCI states/spatial relationships not being enabled by RRC/DCI, a CORESETPoolIndex value of 1 not being set for any CORESET, and no code point in the TCI field being mapped to two TCI states may be read as interchangeable.

In the present disclosure, TRP#1 (first TRP) may correspond to CORESET pool index = 0 or may correspond to the first of two TCI states corresponding to one code point in the TCI field. TRP#2 (second TRP) TRP#1 (first TRP) may correspond to CORESET pool index = 1 or may correspond to the second of two TCI states corresponding to one code point in the TCI field.

In this disclosure, single DCI (sDCI), single PDCCH, multi-TRP system based on single DCI, sDCI-based MTRP, and activation of two TCI states on at least one TCI codepoint may be read as interchangeable.

In the present disclosure, beam instruction DCI, beam instruction MAC CE, and beam instruction DCI/MAC CE may be interpreted as interchangeable. In other words, an instruction regarding the instruction TCI state to the UE may be given using at least one of DCI and MAC CE.

In the present disclosure, channel, signal, and channel/signal may be read as interchangeable. In the present disclosure, DL channel, DL signal, DL signal/channel, transmission/reception of DL signal/channel, DL reception, and DL transmission may be read as interchangeable. In the present disclosure, UL channel, UL signal, UL signal/channel, transmission/reception of UL signal/channel, UL reception, and UL transmission may be read as interchangeable.

In this disclosure, applying TCI state/QCL assumptions to each channel/signal/resource may mean applying TCI state/QCL assumptions to transmission and reception of each channel/signal/resource.

In the present disclosure, the first TRP may correspond to the first TCI state (the first TCI state indicated). In the present disclosure, the second TRP may correspond to the second TCI state (the second TCI state indicated). In the present disclosure, the nth TRP may correspond to the nth TCI state (the nth TCI state indicated).

In the present disclosure, the first CORESET pool index value (e.g., 0), the first TRP index value (e.g., 1), and the first TCI state (first DL/UL (joint/separate) TCI state) may correspond to each other. In the present disclosure, the second CORESET pool index value (e.g., 1), the second TRP index value (e.g., 2), and the second TCI state (second DL/UL (joint/separate) TCI state) may correspond to each other.

Note that in each embodiment of the present disclosure below, the application of multiple TCI states in transmission and reception using multiple TRPs will be mainly described in terms of a method targeting two TRPs (i.e., when at least one of N and M is 2), but the number of TRPs may be three or more (multiple), and each embodiment may be applied to correspond to the number of TRPs. In other words, at least one of N and M may be a number greater than 2.

In this disclosure, schedule, trigger, and activate may be interpreted as interchangeable.

(Wireless communication method)
Each embodiment of the present disclosure may be applied to reception of any DL channel/signal (e.g., PDSCH/A-CSI-RS). In the present disclosure, the PDSCH may be a PDSCH dynamically scheduled by DCI or a semi-persistently scheduled PDSCH (SPS PDSCH).

The following embodiments of the present disclosure may be applied, for example, to a unified TCI state for single DCI-based multi-TRP.

A DCI format for scheduling/activating DL channels/signals (e.g., DCI format 1_1/1-2 (which may be referred to as DL DCI)) may include specific fields (new DCI fields).

The particular field may be a field indicating that one or more (e.g., both/two) indicated TCI states (joint/DL TCI states) are to be applied to the DL channel/signal being scheduled/activated. In other words, the particular field may be a field indicating the number/order of the indicated TCI states to be applied.

The particular field may be represented by a particular number of bits (e.g., 2 bits).

In this disclosure, this particular field may be referred to as a TCI selection field, but the name is not limited to this.

The offset (hereinafter, this may be read as a scheduling offset, a triggering offset, etc.) between the reception of the DL DCI and the reception of the corresponding DL channel/signal may be smaller than a certain threshold. In this case, the UE may buffer the received signal using the indicated TCI state (joint/DL TCI state).

When a DL channel/signal is scheduled by a first DCI format (e.g., DCI format 1_0), if a single frequency network (SFN) scheme (e.g., SFN scheme for PDSCH (RRC parameter sfnSchemePdsch)) is configured, multiple (e.g., both/two) indicated TCI states (joint/DL TCI state) may be applied to the DL channel/signal. Otherwise, one (e.g., first) indicated TCI state (joint/DL TCI state) may be applied to the DL channel/signal.

If a DL channel/signal is scheduled by a second DCI format (e.g., DCI format 1_1/1_2) that does not include a specific field, multiple (e.g., both/two) indicated TCI states (joint/DL TCI states) may be applied to the DL channel/signal.

FIGS. 6A and 6B are diagrams showing other examples of application of indicated TCI states. In the example shown in FIG. 6A, two indicated TCI states (TCI state #1 as the first TCI state and TCI state #2 as the second TCI state) are indicated to the UE.

In the example shown in FIG. 6A, the DL DCI includes a field (TCI selection field) indicating the number/order of the indicated TCI states to be applied. A code point of "00" in this field indicates that the first indicated TCI state is applied. A code point of "01" in this field indicates that the second indicated TCI state is applied. A code point of "10" in this field indicates that the first indicated TCI state and the second indicated TCI state are applied in the order of the first indicated TCI state and the second indicated TCI state. A code point of "11" in this field indicates that the first indicated TCI state and the second indicated TCI state are applied in the order of the second indicated TCI state and the first indicated TCI state.

Figure 6B shows an example where PDSCH is scheduled by DL DCI. The DCI includes a TCI selection field indicating codepoint "00". Therefore, the UE applies TCI state #1 to receive PDSCH (see Figure 6C).

If the offset between the reception of the Scheduling DL DCI and the reception of the scheduled DL channel/signal is greater than (or equal to) a certain threshold, a certain DCI field (e.g., TCI selection field) may indicate the channel/signal to which the indicated TCI state is applied. The operation in this case may be at least one of the following operation 1 and operation 2.

The particular threshold may be, for example, at least one of the existing thresholds (defined up to Rel. 15/16) and values based on RRC parameters/UE capability information defined in Rel. 17/18 and later.

The existing threshold may be, for example, a value based on UE capability information defined in Rel. 15 in a second frequency range (e.g., FR2).

In a first frequency range (e.g., FR1), the particular DCI field may always be included in the DCI.

<<Action 1>>
Certain fields (eg, the TCI selection field) may be included in the DL DCI if certain RRC parameters are configured.

When the code point of a particular field included in a DL DCI (e.g., DCI format 1_1/1_2) indicates a first value (e.g., "00"), the UE may apply a particular indication TCI state (e.g., a first indication (joint/DL) TCI state) to multiple (e.g., all) DL channels/signals (e.g., PDSCH DMRS ports of multiple (all) PDSCH transmission opportunities) scheduled by the DCI.

When the code point of a particular field included in a DL DCI (e.g., DCI format 1_1/1_2) indicates a second value (e.g., "01"), the UE may apply a particular indication TCI state (e.g., a second indication (joint/DL) TCI state) to multiple (e.g., all) DL channels/signals (e.g., PDSCH DMRS ports of multiple (all) PDSCH transmission opportunities) scheduled by the DCI.

When the code point of a specific field included in a DL DCI (e.g., DCI format 1_1/1_2) indicates a third value (e.g., "10"), the UE may apply multiple indication TCI states (e.g., both the first indication (joint/DL) TCI state and the second indication (joint/DL) TCI state) to reception of a DL channel/signal scheduled by the DCI.

For example, when a code point of a particular field included in a DL DCI (e.g., DCI format 1_1/1_2) indicates a third value (e.g., "10"), the multiple indicated TCI states may be applied in a first order (e.g., the first indicated TCI state, then the second indicated TCI state).

When the code point of a specific field included in the DL DCI (e.g., DCI format 1_1/1_2) indicates a fourth value (e.g., "11"), the UE may use a specific method to determine the application of the indicated TCI state.

For example, when the code point of a specific field included in a DL DCI (e.g., DCI format 1_1/1_2) indicates a fourth value (e.g., "11"), the UE may apply multiple indication TCI states (e.g., both the first indication (joint/DL) TCI state and the second indication (joint/DL) TCI state) to reception of a DL channel/signal scheduled by the DCI.

For example, when the code point of a particular field included in a DL DCI (e.g., DCI format 1_1/1_2) indicates a fourth value (e.g., "11"), the multiple indicated TCI states may be applied in a second order (e.g., the second indicated TCI state, then the first indicated TCI state).

The above operation 1 may be applied under a certain condition. The certain condition may be applied, for example, if (if applicable) the offset between at least the reception of the scheduling DL DCI and the reception of the scheduled DL channel/signal is equal to or greater than a certain threshold.

<<Action 2>>
A DL channel/signal may be scheduled by a DL DCI that does not include a specific field (e.g., a TCI selection field). The UE may apply one or more specific indication TCI states to the DL channel/signal.

In this case, the UE may be configured using higher layer signaling (RRC/MAC CE) to apply one or more indicated TCI states (options 0-1). For example, the UE may be configured using specific RRC parameters to apply either a first indicated TCI state, a second indicated TCI state, or both to receive DL channels/signals.

In this case, the UE may also decide to apply the first (or second) indicated TCI state to the reception of the DL channel/signal (options 0-2).

In this case, the UE may also decide to apply multiple indicated TCI states (e.g., both the first indicated TCI state and the second indicated TCI state) to reception of the DL channel/signal (options 0-3).

In this case, the UE may also decide to apply to the DL channel/signal the same indicated TCI state as the indicated TCI state of the PDCCH corresponding to the DL DCI that scheduled the DL channel/signal (options 0-4).

In this case, the UE may also apply the indicated TCI state for one or more TRPs. This may be determined using existing TCI fields (options 0-5).

The above operation 2 may be applied under a certain condition. The certain condition may be applied, for example, if (if applicable) at least the offset between the reception of the Scheduling DL DCI and the reception of the scheduled DL channel/signal is greater than or equal to a certain threshold (e.g., "timeDurationForQCL").

First Embodiment
The first embodiment relates to the application of an indicated TCI state when the scheduling offset is less than a certain threshold.

The UE may determine the application of one or more indicated TCI states to the DL signal based on at least one of the UE capability information regarding the number of buffers for the DL signal and the setting regarding the number of buffers. In the present disclosure, applying an indicated TCI state to a DL signal may mean applying/utilizing the indicated TCI state to perform reception processing (e.g., reception/demodulation/decoding) of the DL signal.

For example, if the scheduling offset is less than a certain threshold, it may be reported (if applicable) whether the UE can buffer (e.g. always buffer) the received signal using multiple (e.g. two) indicated (joint/DL) TCI states.

The report may be made, for example, using UE capability information (e.g., UE capability information regarding the number of buffers for the DL signal).

The first embodiment is broadly divided into embodiments 1-1 and 1-2. The UE/network (NW, for example, a base station) may follow either embodiment 1-1 or 1-2, or may follow a method that combines embodiments 1-1 and 1-2.

The following embodiments 1-1/1-2 may be applied when the scheduling offset is smaller than a certain threshold.

<<Embodiment 1-1>>
The embodiment 1-1 may be applied to a case where a specific UE capability is supported. The specific UE capability may be, for example, a UE capability regarding whether the above-mentioned UE can buffer a received signal (for example, always buffer) using multiple (for example, two) indication (joint/DL) TCI states.

Embodiment 1-1 may be applied when specific higher layer signaling (e.g., RRC parameters/MAC CE (e.g., settings related to the number of buffers for DL signals)) is configured/notified to the UE.

In embodiment 1-1, the UE may buffer the received signal using multiple (e.g., two) indicated TCI states.

DL channels/signals may be scheduled using DL DCI that includes a specific field (e.g., TCI selection field).

The particular field may be included in the DL DCI when a particular RRC parameter is set.

Also, a DL channel/signal may be scheduled using a DL DCI that does not include a specific field (e.g., a TCI selection field). The UE may apply one or more specific indication TCI states to the DL channel/signal.

In this case, the UE may be configured to apply one or more indicated TCI states using higher layer signaling (RRC/MAC CE) (option 1-1-1). For example, the UE may be configured using specific RRC parameters to apply either a first indicated TCI state, a second indicated TCI state, or both to receive DL channels/signals.

In this case, the UE may also decide to apply the first (or second) indicated TCI state to receiving the DL channel/signal (option 1-1-2).

In this case, the UE may also decide to apply multiple indicated TCI states (e.g., both the first indicated TCI state and the second indicated TCI state) to reception of the DL channel/signal (option 1-1-3).

In this case, the UE may also decide to apply to the DL channel/signal the same indicated TCI state as the indicated TCI state of the PDCCH corresponding to the DL DCI that scheduled the DL channel/signal (option 1-1-4).

In this case, the UE may also apply the indicated TCI state for one or more TRPs. This application may be determined using an existing TCI field (option 1-1-5).

When a DL channel/signal is scheduled by a specific DL DCI (e.g., DCI format 1_0), if an SFN scheme (e.g., SFN scheme for PDSCH (e.g., RRC parameter sfnSchemePdsch)) is configured, multiple (e.g., both/two) indicated TCI states (joint/DL TCI states) may apply to the DL channel/signal. Otherwise, one (e.g., first) indicated TCI state (joint/DL TCI state) may apply to the DL channel/signal.

When a DL channel/signal is scheduled by a specific DL DCI (e.g., DCI format 1_0), one (e.g., the first) indicated TCI state (joint/DL TCI state) may be applied to the DL channel/signal, regardless of whether an SFN scheme (e.g., an SFN scheme for PDSCH (e.g., RRC parameter sfnSchemePdsch)) is configured or not.

Figures 7A to 7D are diagrams showing an example of application of the indicated TCI state in embodiment 1-1.

In the example shown in FIG. 7A, two indicated TCI states (TCI state #1 as the first TCI state and TCI state #2 as the second TCI state) are indicated to the UE.

In the example shown in FIG. 7A, the DL DCI includes a field (TCI selection field) indicating the number/order of the indicated TCI states to be applied. A code point of "00" in this field indicates that the first indicated TCI state is applied. A code point of "01" in this field indicates that the second indicated TCI state is applied. A code point of "10" in this field indicates that the first indicated TCI state and the second indicated TCI state are applied in the order of the first indicated TCI state and the second indicated TCI state. A code point of "11" in this field indicates that the first indicated TCI state and the second indicated TCI state are applied in the order of the second indicated TCI state and the first indicated TCI state.

Figure 7B shows an example where a PDSCH is scheduled by a DL DCI. The DCI includes a TCI selection field that indicates codepoint "10".

Figure 7C shows an example of a UE receiving a scheduling DCI and a scheduled PDSCH, and transmitting a PUCCH corresponding to the PDSCH. The DCI indicates that a first indicated TCI state and a second indicated TCI state are to be applied, as shown in Figure 7B. Also, the scheduling offset of the PDSCH scheduled by the DCI is greater than a certain threshold.

At this time, the UE may apply the indicated TCI state according to the above-mentioned operation 1 or operation 2. For example, the UE may determine to apply the first indicated TCI state and the second indicated TCI state to the PDSCH.

Note that in the example shown in FIG. 7C, the first command TCI state (TCI state #1) and the second command TCI state (TCI state #2) are applied to the reception of the PDSCH, but either the first command TCI state or the second TCI state may be applied to the reception of the PDSCH.

Figure 7D shows an example of a UE receiving a scheduling DCI and a scheduled PDSCH, and transmitting a PUCCH corresponding to the PDSCH. The DCI, as shown in Figure 7B, indicates that a first indicated TCI state and a second indicated TCI state are to be applied. Furthermore, the scheduling offset of the PDSCH scheduled by the DCI is smaller than a specific threshold. In this case, the UE can buffer the received signal using multiple indicated TCI states, so that multiple indicated TCI states can be applied even if the scheduling offset is small.

At this time, the UE may apply the indicated TCI state according to at least one of the methods described in embodiment 1-1 above. For example, the UE may determine to apply the first indicated TCI state and the second TCI state to the PDSCH.

Note that in the example shown in FIG. 7D, an example is shown in which the first command TCI state (TCI state #1) and the second command TCI state (TCI state #2) are applied to the reception of the PDSCH, but either the first command TCI state or the second TCI state may be applied to the reception of the PDSCH.

According to embodiment 1-1, the UE can always buffer the received signal using multiple indicated TCI states, and after decoding the DCI, it becomes possible to receive DL channels/signals using one or multiple TCI states depending on the DCI.

<<Embodiment 1-2>>
The first and second embodiments may be applied to a case where a specific UE capability is not supported. The specific UE capability may be, for example, a UE capability regarding whether the above-mentioned UE can buffer (for example, always buffer) a received signal using multiple (for example, two) indication (joint/DL) TCI states.

Embodiments 1-2 may be applied when certain higher layer signaling (e.g., RRC parameters/MAC CE) is not configured/notified to the UE.

In embodiment 1-2, the UE may buffer the received signal using only one indicated TCI state. The one indicated TCI state may be a specific indicated TCI state (e.g., an indicated TCI state having the lowest (or highest) index).

A DL channel/signal may be scheduled using a DL DCI that includes a specific field (e.g., a TCI selection field). A DL channel/signal may be scheduled using a DL DCI that does not include a specific field (e.g., a TCI selection field).

The UE may be configured to apply one or more indicated TCI states using higher layer signaling (RRC/MAC CE) (option 1-2-0). For example, the UE may be configured using specific RRC parameters/settings to apply either a first indicated TCI state or a second indicated TCI state to reception of DL channels/signals.

The UE may be configured to apply one or more indicated TCI states using higher layer signaling (RRC/MAC CE) (option 1-2-1). For example, the UE may be configured using specific RRC parameters/settings to apply either a first indicated TCI state, a second indicated TCI state, or both to receive DL channels/signals.

In this case, the UE may also determine to apply the first (or second) indicated TCI state to the reception of the DL channel/signal (option 1-2-2). In this case, the UE may also determine to apply the indicated TCI state corresponding to a specific DCI field code point (e.g., the lowest (or highest) TCI selection field code point) to the reception of the DL channel/signal (option 1-2-2').

In this case, the UE may also decide to apply multiple indicated TCI states (e.g., both the first indicated TCI state and the second indicated TCI state) to reception of the DL channel/signal (option 1-2-3).

In this case, the UE may also decide to apply to the DL channel/signal the same indicated TCI state as the indicated TCI state of the PDCCH corresponding to the DL DCI that scheduled the DL channel/signal (option 1-2-4).

In this case, the UE may also apply the indicated TCI state for one or more TRPs. This application may be determined using an existing TCI field (option 1-2-5).

Figures 8A to 8D are diagrams showing an example of application of the indicated TCI state in

embodiments

1 and 2.

The examples shown in Figures 8A and 8B are similar to those in Figures 7A and 7B described above, so a detailed explanation will be omitted.

Figure 8C shows an example of a UE receiving a scheduling DCI and a scheduled PDSCH, and transmitting a PUCCH corresponding to the PDSCH. The DCI indicates that a first indicated TCI state and a second indicated TCI state are to be applied, as shown in Figure 8B. Also, the scheduling offset of the PDSCH scheduled by the DCI is greater than a certain threshold.

Note that in the example shown in FIG. 8C, an example is shown in which the first indicated TCI state (TCI state #1) and the second indicated TCI state (TCI state #2) are applied to the reception of the PDSCH, but either the first indicated TCI state or the second TCI state may be applied to the reception of the PDSCH.

Figure 8D shows an example of a UE receiving a scheduling DCI and a scheduled PDSCH, and transmitting a PUCCH corresponding to the PDSCH. The DCI, as shown in Figure 8B, indicates that a first indicated TCI state and a second indicated TCI state are to be applied. Furthermore, the scheduling offset of the PDSCH scheduled by the DCI is smaller than a specific threshold. In this case, the UE can buffer the received signal using only one indicated TCI state, so that when the scheduling offset is smaller than the threshold, only one indicated TCI state can be applied.

At this time, the UE may apply the indicated TCI state according to at least one of the options described in the above embodiment 1-2. For example, the UE may determine to apply only the first indicated TCI state (or the second TCI state) to the PDSCH. In other words, the UE ignores the instruction regarding the application of the indicated TCI state 1 and the second indicated TCI state included in the DCI.

Note that embodiments 1-2 may be applied to any type of DCI format, regardless of whether or not specific fields are present.

According to embodiment 1-2, the TCI state of the received signal buffered in the UE is one, so the UE operation can be made common regardless of the type of DCI format and the presence or absence of specific fields, making it possible to simplify the implementation of the UE.

<Modification of the first embodiment>
The above embodiments 1-1 and 1-2 may be switched and applied based on UE capabilities (information)/RRC settings.

Either of the above embodiments 1-1 and 1-2 may be specified in the specifications. For example, multiple (e.g., all) UEs may operate according to embodiment 1-1 (or embodiment 1-2).

Furthermore, for a UE that supports the UE capability, any of the operations in the above embodiments 1-1 and 1-2 may be configured/notified using higher layer signaling (RRC/MAC CE).

For example, the UE may report to the NW that it supports the UE capability. The NW may then configure/notify the operation of any of the embodiments 1-1 and 1-2 using RRC signaling/MAC CE.

For example, even if it is reported that the UE capability is supported, the UE may be configured/notified of the operation according to embodiment 1-2.

The first embodiment may be applied in a specific frequency range (e.g., at least one of FR1, FR2, FR3, FR4, FR5, FR2-1, and FR2-2).

The above first embodiment describes the indicated TCI state applied to the PDSCH, but it can also be applied to the reception of the A-CSI-RS in the same way.

For example, in embodiment 1-1, the UE buffers DL signals using multiple (e.g., two) indicated (joint/DL) TCI states, and one of the indicated TCI states may be applied to the A-CSI-RS.

At this time, the command TCI state to be applied to the A-CSI-RS may be switched using a specific field (TCI selection field) included in the triggering DCI, or the command TCI state may be selected based on a specific rule (for example, the first (or second) command TCI state may always be selected).

For example, in embodiment 1-2, the UE buffers the DL signal using one indicated TCI state, and the one indicated TCI state may be applied to receiving the A-CSI-RS.

The rules for selecting one TCI state for the A-CSI-RS may be the same as the rules for the PDSCH.

<Additional Information>
[Notification of information to UE]
In the above-described embodiments, any information may be notified to the UE (from a network (NW) (e.g., a base station (BS))) (in other words, any information is received by the UE from the BS) using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal/channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

When the above notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader that is not specified in existing standards.

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

Furthermore, notification of any information to the UE in the above-mentioned embodiments may be performed periodically, semi-persistently, or aperiodically.

[Information notification from UE]
In the above-described embodiments, notification of any information from the UE (to the NW) (in other words, transmission/report of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal/channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.

If the notification is made by a MAC CE, the MAC CE may be identified by including a new LCID in the MAC subheader that is not specified in existing standards.

If the notification is made by UCI, the notification may be transmitted using PUCCH or PUSCH.

Furthermore, in the above-mentioned embodiments, notification of any information from the UE may be performed periodically, semi-persistently, or aperiodically.

[Application of each embodiment]
At least one of the above-mentioned embodiments may be applied when a specific condition is satisfied, which may be specified in a standard or may be notified to a UE/BS using higher layer signaling/physical layer signaling.

At least one of the above-described embodiments may be applied only to UEs that have reported or support a particular UE capability.

The specific UE capabilities may indicate at least one of the following:
Supporting specific processing/operations/control/information for at least one of the above embodiments (eg, buffering received signals using multiple indicated TCI states).
Number of bufferable receive signal indication TCI states supported.

Furthermore, the above-mentioned specific UE capabilities may be capabilities that are applied across all frequencies (commonly regardless of frequency), capabilities per frequency (e.g., one or a combination of a 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 (SubCarrier Spacing (SCS)), or capabilities per Feature Set (FS) or Feature Set Per Component-carrier (FSPC).

The specific UE capabilities may be capabilities that are applied across all duplexing methods (commonly regardless of the duplexing method), or may be capabilities for each duplexing method (e.g., Time Division Duplex (TDD) and Frequency Division Duplex (FDD)).

Furthermore, at least one of the above-mentioned embodiments may be applied when the UE configures/activates/triggers specific information related to the above-mentioned embodiments (or performs the operations of the above-mentioned embodiments) by higher layer signaling/physical layer signaling. For example, the specific information may be information indicating enabling a buffer of a received signal using multiple indicated TCI states, any RRC parameter for a specific release (e.g., Rel. 18/19), etc.

If the UE does not support at least one of the above specific UE capabilities or the above specific information is not configured, the UE may, for example, apply Rel. 15/16 operations.

(Additional Note)
With respect to one embodiment of the present disclosure, the following invention is noted.
[Appendix 1]
a control unit that controls a buffer of the downlink signal using one or more command transmission configuration indication (TCI) states based on at least one of a report of capability information regarding the number of buffers of the downlink signal and a setting regarding the number of buffers, when an offset between reception of downlink control information for scheduling a downlink signal and reception of the downlink signal is smaller than a specific threshold value;
A terminal having a receiving unit that performs receiving processing of the downlink signal by using the one or more indicated TCI states.
[Appendix 2]
The terminal according to claim 1, wherein, when the control unit reports the capability information, the control unit applies the plurality of designated TCI states to the downlink signal based on a specific field included in the downlink control information.
[Appendix 3]
The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the control unit applies the one indication TCI state to the downlink signal based on a configuration of higher layer signaling when the capability information is not reported.
[Appendix 4]
The terminal according to any one of Supplementary Note 1 to Supplementary Note 3, wherein the control unit always applies the one designated TCI state to the downlink signal when the capability information is not reported.

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

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

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

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.

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

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

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

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

In addition, the user terminal 20 may communicate using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.

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

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

The core network 30 may include network functions (Network Functions (NF)) such as, for example, a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Note that multiple functions may be provided by one network node. In addition, communication with an external network (e.g., the Internet) may be performed via the DN.

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

In the wireless communication system 1, a wireless access method based on Orthogonal Frequency Division Multiplexing (OFDM) may be used. For example, in at least one of the downlink (DL) and uplink (UL), Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), etc. may be used.

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

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

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

User data, upper layer control information, System Information Block (SIB), etc. are transmitted via PDSCH. User data, upper layer control information, etc. may also be transmitted via PUSCH. Furthermore, Master Information Block (MIB) may also be transmitted via PBCH.

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

Note that the DCI for scheduling the PDSCH may be called a DL assignment or DL DCI, and the DCI for scheduling the PUSCH may be called a UL grant or UL DCI. Note that the PDSCH may be interpreted as DL data, and the PUSCH may be interpreted as UL data.

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

A search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," "CORESET setting," etc. in this disclosure may be read as interchangeable.

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

Note that in this disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

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

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

In addition, in the wireless communication system 1, a measurement reference signal (Sounding Reference Signal (SRS)), a demodulation reference signal (DMRS), etc. may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific Reference Signal).

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

Note that this example mainly shows the functional blocks of the characteristic parts of this embodiment, and the base station 10 may also be assumed to have other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

The control unit 110 controls the entire base station 10. The control unit 110 can be configured from a controller, a control circuit, etc., which are described based on a common understanding in the technical field to which this disclosure pertains.

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

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

The transceiver unit 120 may be configured as an integrated transceiver unit, or may be composed of a transmission unit and a reception unit. The transmission unit may be composed of a transmission processing unit 1211 and an RF unit 122. The reception unit may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.

The transmitting/receiving antenna 130 can be configured as an antenna described based on common understanding in the technical field to which this disclosure pertains, such as an array antenna.

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

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

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

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

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

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

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

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

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

Note that the transmitter and receiver of the base station 10 in this disclosure may be configured with at least one of the transmitter/receiver 120, the transmitter/receiver antenna 130, and the transmission path interface 140.

When the offset between the reception of downlink control information that schedules a downlink signal and the reception of the downlink signal is less than a certain threshold, the control unit 110 may instruct the buffering of the downlink signal using one or more instruction transmission configuration indication (TCI) states by using at least one of a report of capability information regarding the number of buffers for the downlink signal and a setting regarding the number of buffers. The transceiver unit 120 may transmit the downlink signal using the one or more instruction TCI states.

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

Note that this example mainly shows the functional blocks of the characteristic parts of this embodiment, and the user terminal 20 may also be assumed to have other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

The control unit 210 controls the entire user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which are described based on a common understanding in the technical field to which this disclosure pertains.

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

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

The transceiver unit 220 may be configured as an integrated transceiver unit, or may be composed of a transmission unit and a reception unit. The transmission unit may be composed of a transmission processing unit 2211 and an RF unit 222. The reception unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

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

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

The transceiver 220 may form at least one of the transmit beam and receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc.

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

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

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

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

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

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

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

The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. The channel measurement resources may be, for example, non-zero power (NZP) CSI-RS resources. The measurement unit 223 may derive interference measurements for CSI calculation based on interference measurement resources. The interference measurement resources may be at least one of NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. CSI-IM may be called CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be read as interchangeable.

In addition, the transmitting unit and receiving unit of the user terminal 20 in this disclosure may be configured by at least one of the transmitting/receiving unit 220 and the transmitting/receiving antenna 230.

When the offset between the reception of downlink control information for scheduling a downlink signal and the reception of the downlink signal is less than a specific threshold, the control unit 210 may control the buffering of the downlink signal using one or more command transmission configuration indication (TCI) states based on at least one of a report of capability information regarding the number of buffers for the downlink signal and a setting regarding the number of buffers. The transceiver unit 220 may perform reception processing of the downlink signal using the one or more command TCI states.

When the control unit 210 reports the capability information, the control unit 210 may apply the multiple indicated TCI states to the downlink signal based on a specific field included in the downlink control information.

If the control unit 210 does not report the capability information, the control unit 210 may apply the one indicated TCI state to the downlink signal based on the configuration of higher layer signaling.

If the control unit 210 does not report the capability information, it may always apply the one indicated TCI state to the downlink signal.

(Hardware configuration)
The block diagrams used in the description of the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. 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 may be realized using two or more devices that are physically or logically separated and directly or indirectly connected (for example, using wires, wirelessly, etc.). The functional blocks may be realized by combining the one device or the multiple devices with software.

Here, the functions include, but are not limited to, judgement, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the transmission function may be called a transmitting unit, a transmitter, and the like. In either case, as mentioned above, there are no particular limitations on the method of realization.

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

In addition, in this disclosure, the terms apparatus, circuit, device, section, unit, etc. may be interpreted as interchangeable. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the figures, or may be configured to exclude some of the devices.

For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, sequentially, or using other techniques. Furthermore, the processor 1001 may be implemented by one or more chips.

The functions of the base station 10 and the user terminal 20 are realized, for example, by loading specific software (programs) onto hardware such as the processor 1001 and memory 1002, causing the processor 1001 to perform calculations, control communications via the communication device 1004, and control at least one of the reading and writing of data in the memory 1002 and storage 1003.

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

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

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

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

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

The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one structure (e.g., a touch panel).

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 may be configured using different buses between each device.

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

(Modification)
In addition, the terms described in this disclosure and the terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be read as mutually interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may be called a pilot, a pilot signal, or the like depending on the applied standard. A component carrier (CC) may also be called a cell, a frequency carrier, a carrier frequency, or the like.

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

Here, the numerology may be a communication parameter that is applied to at least one of the transmission and reception of a signal or channel. The numerology may indicate, for example, at least one of the following: SubCarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame configuration, a specific filtering process performed by the transceiver in the frequency domain, a specific windowing process performed by the transceiver in the time domain, etc.

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

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

A radio frame, subframe, slot, minislot, and symbol all represent time units when transmitting a signal. A different name may be used for radio frame, subframe, slot, minislot, and symbol. Note that the time units such as frame, subframe, slot, minislot, and symbol in this disclosure may be read as interchangeable.

For example, one subframe may be called a TTI, multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. In other words, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

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

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

Note that when one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. In addition, the number of slots (minislots) that constitute the minimum time unit of scheduling may be controlled.

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

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

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

Furthermore, an RB may include one or more symbols in the time domain and may be one slot, one minislot, one subframe, or one TTI in length. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

In addition, one or more RBs may be referred to as a physical resource block (Physical RB (PRB)), a sub-carrier group (Sub-Carrier Group (SCG)), a resource element group (Resource Element Group (REG)), a PRB pair, an RB pair, etc.

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

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

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

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

Note that the above-mentioned structures of radio frames, subframes, slots, minislots, and symbols are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, as well as the number of symbols in a TTI, the symbol length, and the cyclic prefix (CP) length can be changed in various ways.

In addition, the information, parameters, etc. described in this disclosure may be represented using absolute values, may be represented using relative values from a predetermined value, or may be represented using other corresponding information. For example, a radio resource may be indicated by a predetermined index.

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

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

In addition, information, signals, etc. may be output from a higher layer to a lower layer and/or from a lower layer to a higher layer. Information, signals, etc. may be input/output via multiple network nodes.

Input/output information, signals, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. Input/output information, signals, etc. may be overwritten, updated, or added to. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

The notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods. For example, the notification of information in this disclosure may be performed 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)), etc.), Medium Access Control (MAC) signaling), other signals, or a combination of these.

The physical layer signaling may be called Layer 1/Layer 2 (L1/L2) control information (L1/L2 control signal), L1 control information (L1 control signal), etc. The RRC signaling may be called an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc. The MAC signaling may be notified, for example, using a MAC Control Element (CE).

Furthermore, notification of specified information (e.g., notification that "X is the case") is not limited to explicit notification, but may be implicit (e.g., by not notifying the specified information or by notifying other information).

The determination may be based on a value represented by a single bit (0 or 1), a Boolean value represented by true or false, or a comparison of numerical values (e.g., with a predetermined value).

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

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

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

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

In the present disclosure, the antenna port may be interchangeably read as an antenna port for any signal/channel (e.g., a demodulation reference signal (DMRS) port). In the present disclosure, the resource may be interchangeably read as a resource for any signal/channel (e.g., a reference signal resource, an SRS resource, etc.). The resource may include time/frequency/code/space/power resources. The spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

The above groups may include, for example, at least one of a spatial relationship group, a Code Division Multiplexing (CDM) group, a Reference Signal (RS) group, a Control Resource Set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, a panel group, etc.

Furthermore, in this disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be interpreted as interchangeable.

Furthermore, in this disclosure, the terms TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc. may be interpreted as interchangeable.

Furthermore, in this disclosure, "QCL", "QCL assumptions", "QCL relationship", "QCL type information", "QCL property/properties", "specific QCL type (e.g., Type A, Type D) characteristics", "specific QCL type (e.g., Type A, Type D)", etc. may be read as interchangeable.

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

Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be interchangeable. "Spatial relationship information (TCI state)" may be interchangeable as "set of spatial relationship information (TCI state)", "one or more pieces of spatial relationship information", etc. TCI state and TCI may be interchangeable. Spatial relationship information and spatial relationship may be interchangeable.

In this disclosure, terms such as "Base Station (BS)", "Radio base station", "Fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "Access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission/Reception Point (TRP)", "Panel", "Cell", "Sector", "Cell group", "Carrier", "Component carrier", etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services by a base station subsystem (e.g., a small base station for indoor use (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the entire coverage area of at least one of the base station and base station subsystems that provide communication services in this coverage.

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

In this disclosure, terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", and "terminal" may be used interchangeably.

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

At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. In addition, at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.

The moving body in question refers to an object that can move, and the moving speed is arbitrary, and of course includes the case where the moving body is stationary. The moving body in question includes, but is not limited to, 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, artificial satellites, drones, multicopters, quadcopters, balloons, and objects mounted on these. The moving body in question may also be a moving body that moves autonomously based on an operating command.

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

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

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

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

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

The information service unit 59 is composed of various devices, such as a car navigation system, audio system, speakers, displays, televisions, and radios, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via the communication module 60, etc., to provide various information/services (e.g., multimedia information/multimedia services) to the occupants of the vehicle 40.

The information service unit 59 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that perform output to the outside.

The driving assistance system unit 64 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving load, such as a millimeter wave radar, a Light Detection and Ranging (LiDAR), a camera, a positioning locator (e.g., a Global Navigation Satellite System (GNSS)), map information (e.g., a High Definition (HD) map, an Autonomous Vehicle (AV) map, etc.), a gyro system (e.g., an Inertial Measurement Unit (IMU), an Inertial Navigation System (INS), etc.), an Artificial Intelligence (AI) chip, and an AI processor, and one or more ECUs that control these devices. The driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize a driving assistance function or an autonomous driving function.

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

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

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

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

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

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

Similarly, the user terminal in this disclosure may be interpreted as a base station. In this case, the base station 10 may be configured to have the functions of the user terminal 20 described above.

In this disclosure, operations that are described as being performed by a base station may in some cases also be performed by its upper node. In a network that includes one or more network nodes having base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME) or a Serving-Gateway (S-GW)), or a combination of these.

Each aspect/embodiment described in this disclosure may be used alone, in combination, or switched between depending on the implementation. In addition, the processing procedures, sequences, flow charts, etc. of each aspect/embodiment described in this disclosure may be rearranged as long as there is no inconsistency. For example, the methods described in this disclosure present elements of various steps using an exemplary order, and are not limited to the particular order presented.

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

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

Any reference to an element using a designation such as "first," "second," etc., 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 method of distinguishing between two or more elements. Thus, a reference to a first and second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.

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

"Determining" may also be considered to mean "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), etc.

Furthermore, "judgment (decision)" may be considered to mean "judging (deciding)" resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" may be considered to mean "judging (deciding)" some kind of action. In this disclosure, "judgment (decision)" may be interpreted interchangeably with the actions described above.

Furthermore, in this disclosure, "determine/determining" may be interpreted interchangeably as "assume/assuming," "expect/expecting," "consider/considering," etc. Furthermore, in this disclosure, "does not expect to do..." may be interpreted interchangeably as "assumes not to do...."

In the present disclosure, "expect" may be read as "be expected". For example, "expect(s)..." ("..." may be expressed, for example, as a that clause, a to infinitive, etc.) may be read as "be expected...". "does not expect..." may be read as "be not expected...". Also, "An apparatus A is not expected..." may be read as "An apparatus B other than apparatus A does not expect..." (for example, if apparatus A is a UE, apparatus B may be a base station).

The "maximum transmit power" referred to in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

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

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

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

When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Additionally, the term "or," as used in this disclosure, is not intended to be an exclusive or.

In this disclosure, where articles have been added through translation, such as a, an, and the in English, this disclosure may include that the nouns following these articles are plural.

In this disclosure, terms such as "less than", "less than", "greater than", "more than", "equal to", etc. may be read as interchangeable. In addition, in this disclosure, terms meaning "good", "bad", "big", "small", "high", "low", "fast", "slow", "wide", "narrow", etc. may be read as interchangeable, not limited to positive, comparative and superlative. In addition, in this disclosure, terms meaning "good", "bad", "big", "small", "high", "low", "fast", "slow", "wide", "narrow", etc. may be read as interchangeable, not limited to positive, comparative and superlative, as expressions with "ith" (i is any integer) (for example, "best" may be read as "ith best").

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

In the present disclosure, "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", "B until A" and the like may be read as interchangeable. Note that A, B, etc. here may be replaced with appropriate expressions such as nouns, gerunds, and normal sentences depending on the context. Note that the time difference between A and B may be almost 0 (immediately after or immediately before). Also, a time offset may be applied to the time when A occurs. For example, "A" may be read interchangeably as "before/after the time offset at which A occurs." The time offset (e.g., one or more symbols/slots) may be predefined or may be identified by the UE based on signaled information.

In this disclosure, timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc. may be interpreted as interchangeable.

The invention disclosed herein has been described in detail above, but it is clear to those skilled in the art that the invention disclosed herein is not limited to the embodiments described herein. The description of the present disclosure is intended for illustrative purposes only and does not imply any limitation on the invention disclosed herein.

This application is based on Patent Application No. 2023-29564, filed February 28, 2023, the contents of which are incorporated herein in their entirety.

Claims

a control unit that controls a buffer of the downlink signal using one or more command transmission configuration indication (TCI) states based on at least one of a report of capability information regarding the number of buffers of the downlink signal and a setting regarding the number of buffers, when an offset between reception of downlink control information for scheduling a downlink signal and reception of the downlink signal is smaller than a specific threshold value;
A terminal having a receiving unit that performs receiving processing of the downlink signal by using the one or more indicated TCI states.
The terminal according to claim 1, wherein the control unit, when reporting the capability information, applies the plurality of indicated TCI states to the downlink signal based on a specific field included in the downlink control information.
The terminal according to claim 1, wherein the control unit applies the one indicated TCI state to the downlink signal based on a setting of higher layer signaling when the capability information is not reported.
The terminal according to claim 1, wherein the control unit always applies the one indicated TCI state to the downlink signal when the capability information is not reported.
When an offset between reception of downlink control information for scheduling a downlink signal and reception of the downlink signal is less than a certain threshold, controlling a buffer of the downlink signal using one or more command transmission configuration indication (TCI) states based on at least one of a report of capability information regarding the number of buffers of the downlink signal and a configuration regarding the number of buffers;
and performing reception processing of the downlink signal using the one or more indicated TCI states.
a control unit that, when an offset between reception of downlink control information for scheduling a downlink signal and reception of the downlink signal is smaller than a specific threshold, instructs buffering of the downlink signal using one or more command transmission configuration indication (TCI) states by using at least one of a report of capability information regarding the number of buffers of the downlink signal and a setting regarding the number of buffers;
A base station comprising: a transmitter that transmits the downlink signal using the one or more indicated TCI states.