WO2025169266A1 - Terminal, wireless communication method, and base station - Google Patents

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives at least one of a MAC control element (MAC CE) and downlink control information indicating a plurality of indicated transmission configuration indication (TCI) states; and a control unit that controls at least one of downlink reception and uplink transmission on the basis of the plurality of indicated TCI states. Upon receiving information indicating a subset of a plurality of indicated TCI states, the control unit updates some indicated TCI states of the plurality of indicated TCI states on the basis of the information indicating the subset, and maintains the remaining indicated TCI states.

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 even higher data rates and lower latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was specified with the aim of achieving even greater capacity and sophistication over LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8 and 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 or later, etc.) are also being considered.

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

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

Wireless communication systems from Rel. 17 onwards will support a unified TCI state, and wireless communication systems from Rel. 18 onwards are expected to support the indication of a unified TCI state (e.g., multiple TCI states) for multiple transmitting and receiving points.

However, when the indication/application of multiple indication TCI states is supported, there has been insufficient consideration given to how to control the indication/update of each indication TCI state.

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

A terminal according to one aspect of the present disclosure has a receiving unit that receives at least one of downlink control information and MAC Control Elements (MAC CEs) that indicate multiple indicated Transmission Configuration Indication (TCI) states, and a control unit that controls at least one of downlink reception and uplink transmission based on the multiple indicated TCI states. When the control unit receives information indicating a subset of the multiple indicated TCI states, the control unit updates the indicated TCI states of some of the multiple indicated TCI states based on the information indicating the subset, and maintains the remaining indicated TCI states.

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

1A and 1B show an example of a unified/common TCI framework. 2A and 2B show an example of DCI-based TCI status indication. 3A to 3D are diagrams showing an example of a multi-TRP. 4A-4C are diagrams illustrating an example of application of an indicated TCI state. FIG. 5 is a diagram showing an example of mapping between TCI code points and multiple joint TCI states when multiple indicated TCI states (joint) are indicated. FIG. 6 is a diagram illustrating an example of update control of the indicated TCI state according to the first embodiment. FIG. 7 is a diagram illustrating an example of update control of the indicated TCI state according to the second embodiment. Figure 8 shows an example of a MAC CE for activation/deactivation of the unified TCI state. Figure 9 shows another example of a MAC CE for activation/deactivation of the unified TCI state. FIG. 10 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 11 is a diagram illustrating an example of the configuration of a base station according to an embodiment. FIG. 12 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. FIG. 13 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. FIG. 14 is a diagram illustrating an example of a vehicle according to an embodiment.

(TCI, spatial relationships, 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 the UE of at least one of the signal and the channel (referred to as the signal/channel) based on the transmission configuration indication state (TCI state).

TCI states may refer to those that apply to downlink signals/channels. The equivalent of TCI states that apply to uplink signals/channels may be expressed as spatial relations.

TCI status is information about the quasi-co-location (QCL) of signals/channels, and may also be called spatial reception parameters, spatial relation information, etc. The TCI status may be set in the UE for each channel or signal.

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 the same between these different signals/channels (i.e., they have QCL with respect to at least one of these).

Note that the spatial reception parameters may correspond to the reception beam of the UE (e.g., a reception analog beam), and the beam may be identified based on the spatial QCL. In this disclosure, the QCL (or at least one element of the QCL) 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 with different parameters (or parameter sets) that can be assumed to be identical.

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

The UE may determine at least one of the transmit beam (Tx beam) and 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 following: a downlink shared channel (Physical Downlink Shared Channel (PDSCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), an uplink shared channel (Physical Uplink Shared Channel (PUSCH)), and an uplink control channel (Physical Uplink Control Channel (PUCCH)).

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

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.

[Data Physical Layer Procedures/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 upper layer parameter qcl-Type1 for the first DL RS and the upper layer parameter 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 upper layer parameter qcl-Type in QCL-Info and takes 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 Status]
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.

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

One common beam for both DL and UL, or one common beam for DL and one common beam for UL (two common beams in total) 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 (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 using 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 from the X active TCI states. The selected TCI state may apply to both UL and DL channels/RS.

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

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, or 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 a TCI state common to one UL and DL for a single TRP is notified/configured/instructed to the UE (joint TCI state for a single TRP).

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

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

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

In the above example, the values of N and M were described as 1 or 2, but the values of N and M may be 3 or greater, and N and M may be different.

Support for N=M=1 is being considered for Rel. 17. Support for other cases is being considered for Rel. 18 and later.

In the example of Figure 1A, RRC parameters (information elements) configure multiple TCI states for both DL and UL. The MAC CE may activate multiple TCI states from the configured multiple TCI states. 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 shown in this figure, a single point may represent one TCI state that applies to both UL and DL, or 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).

Note that in the present disclosure, 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 the present disclosure, being instructed to set one of multiple TCI states using DCI may mean receiving instruction information that indicates one of the multiple TCI states included in the DCI, or simply receiving "instruction information."

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

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

In Rel. 17 NR and later, it is assumed that 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 MAC CE/DCI will support indicative serving cell change to a cell with a different PCI.

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

If DLorJointTCIState or UL-TCIState (UL TCI state) is not configured in the BWP in that CC, the UE can apply the DLorJointTCIState or UL-TCIState configuration from the reference BWP of the reference CC. If the UE has DLorJointTCIState or UL-TCIState configured in any CC in the same band, it is not assumed that TCI-State, SpatialRelationInfo (spatial relation information), or PUCCH-SpatialRelationInfo (PUCCH spatial relation information) in that band are configured, except for SpatialRelationInfoPos (spatial relation information for position). The UE assumes that if the UE has TCI-State set in any CC in the CC list by simultaneousTCI-UpdateList1-r16 (simultaneous TCI update list 1), simultaneousTCI-UpdateList2-r16 (simultaneous TCI update list 2), simultaneousSpatial-UpdatedList1-r16 (simultaneous spatial update list 1), or simultaneousSpatial-UpdatedList2-r16 (simultaneous spatial update list 2), the UE does not have DLorJointTCIState or UL-TCIState set in any CC in that CC.

The UE receives an activation command used to map up to eight TCI states and/or TCI state pairs, with one TCI state for the DL channel/signal and one TCI state for the UL channel/signal, to code points in the DCI field 'Transmission Configuration Indication' (TCI) for one CC/DL BWP or set of CCs/DL BWPs, if available. When a set of TCI state IDs is activated for a set of CCs/DL BWPs, and, if available, for one of the CCs/DL BWPs, the same set of TCI state IDs applies to all DL and/or UL BWPs within the indicated CC, where the applicable list of CCs is determined by the CC indicated in the activation command. If the activation command maps DLorJointTCIState and/or UL-TCIState to only one TCI codepoint, 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 one single TCI codepoint 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 assumes 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

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

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 Mode 2/Mode 3 above may also be referred to as beam instruction DCI.

In Rel. 15/16, if the UE does not support active BWP changes via DCI, the UE ignores the BWP indicator field. Similar behavior is being considered for the relationship between Rel. 17 TCI state support and TCI field interpretation. If the UE is configured with Rel. 17 TCI state, the TCI field will always be present in DCI format 1_1/1_2; if the UE does not support TCI updates 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 configured for each CORESET.

The TCI field in DCI format 1_1 is 0-bit if the higher layer parameter tci-PresentInDCI is not enabled, and 3-bit otherwise. If the BWP indicator field indicates a BWP other than the active BWP, the UE shall follow the following 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 within the indicated BWP; otherwise, the UE shall assume that tci-PresentInDCI is enabled for all CORESETs within 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 state/Set TCI state)
For Rel. 17 TCI states, the unified/common TCI state may refer to the Rel. 17 TCI state indicated using (Rel. 17) DCI/MAC CE/RRC (indicated Rel. 17 TCI state).

In 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 of PDSCH/PDCC (updated using Rel. 17 DCI/MAC CE/RRC), PUSCH of dynamic grant (DCI)/configured grant, and multiple (e.g., all) dedicated PUCCH resources. The TCI state indicated by DCI/MAC CE/RRC may be referred to as the indicated TCI state or the unified TCI state.

With regard 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 (Rel. 17) MAC CE/RRC (configured Rel. 17 TCI state). In this disclosure, the terms configured Rel. 17 TCI state, 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 interpreted interchangeably.

The configured Rel. 17 TCI state may not be shared with at least one of the UE-specific reception on 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 RRC/MAC CE per CORESET/per resource/per resource set, and may not be updated even if the indicated Rel. 17 TCI state (common TCI state) is updated.

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 per CORESET/per resource/per resource set using RRC/MAC CE. It is also being considered that the UE will make decisions regarding this 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 this update based on specific parameters.

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

In addition, with regard to intra-cell beam indication (TCI state indication), it is being considered to support Rel. 17 TCI state indication for UE-specific CORESETs and the PDSCHs associated with those CORESETs, as well as non-UE-specific CORESETs and the PDSCHs associated with those CORESETs.

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

In Rel. 15, whether or not to instruct the TCI state for CORESET #0 was up to the base station's implementation. In Rel. 15, for CORESET #0 for which a TCI state is instructed, the instructed TCI state is applied. For CORESET #0 for which a TCI state is not instructed, the SSB and QCL selected at the time of the most recent PRACH transmission are applied.

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

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

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

For CORESET #0, a CORESET with a common search space (CSS), and a CORESET with a CSS and a UE-specific search space (USS), whether to follow the 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 apply to that CORESET.

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

(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 applies. Otherwise, the Rel. 15 specifications apply for that CORESET. That is, CORESET0 follows the TCI state activated by the MAC CE or is QCL'd with SSB.
For CORESETs with index other than 0 with USS/CSS type 3, the indicated TCI state always applies.
For a CORESET with an index other than 0, with at least a CSS other than CSS type 3, configured to follow the unified TCI state, the indicated TCI state applies. Otherwise, the configured TCI state for that CORESET applies to that CORESET.

[PDSCH]
- The indication TCI state always applies for all UE-dedicated PDSCHs.
For a non-UE-dedicated PDSCH (a PDSCH scheduled by a DCI in the CSS), if followUnifiedTCIState is set (for the CORESET of the PDCCH that schedules that PDSCH), the indicated TCI state may apply. Otherwise, the configured TCI state for that PDSCH applies to that 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 that PDSCH.

[CSI-RS]
For an A-CSI-RS for CSI acquisition or beam management, if followUnifiedTCIState is set (for 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 indication TCI state is always applied.

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

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

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

Figures 3A-3D show examples of multi-TRP scenarios. In these examples, it is assumed that each TRP can transmit four different beams, but this is not limited to this example.

Figure 3A shows an example of a case where only one TRP (TRP1 in this example) of multiple TRPs transmits to the UE (this may be referred to as single mode, single TRP, etc.). In this case, TRP1 transmits both control signals (PDCCH) and data signals (PDSCH) to the UE.

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

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

Figure 3C shows an example of a case where each of the multi-TRPs transmits a part of the control signal to the UE, and the multi-TRP transmits a data signal (this may be called master-slave mode). Part 1 of the control signal (DCI) may be transmitted on TRP1, and part 2 of the control signal (DCI) may be transmitted on TRP2. 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 the DCI.

Figure 3D shows an example of a case where each of the multi-TRPs transmits a separate control signal to the UE, and the multi-TRPs transmit data signals (this may be called 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 multiple TRPs such as those shown in Figure 3B (which may also be called multiple PDSCHs) are scheduled using a single DCI, the DCI may be called a single DCI (S-DCI, single PDCCH). Also, when multiple PDSCHs from multiple TRPs such as those shown in Figure 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)/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 layer maps a first codeword to transmit a first PDSCH using a first number of layers (e.g., two layers) with a first precoding. Furthermore, TRP2 modulates and layer maps a second codeword to transmit a second PDSCH using a second number of layers (e.g., two layers) with a second precoding.

Note that multiple PDSCHs (multi-PDSCHs) that are NCJTed may be defined as partially or completely overlapping in 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 in at least one of the time and frequency resources.

The first PDSCH and 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 will be supported. It is considered that repetition schemes (URLLC schemes, for example, schemes 1, 2a, 2b, 3, and 4) across multi-TRP in the frequency domain, layer (spatial) domain, or time domain will be 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 within one slot. In scheme 4, multiple PDSCHs from multiple TRPs are transmitted within different slots.

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

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

For single PDCCH designs (mainly for ideal backhaul), TCI extensions are being considered. Each TCI code point in the DCI may correspond to one or two TCI states. The TCI field size may be the same as that in Rel. 15.

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

With regard to the PDCCH/CORESET enhancements specified in Rel. 16, in multi-TRP based on multi-DCI, a CORESET pool index is configured for each CORESET.

(TCI Selection Field)
A specific field (new DCI field) may be included in a DCI format (eg, DCI format 1_1/1-2 (which may be referred to as DL DCI)) for scheduling/activating/triggering DL channels/signals.

The specific field may be a field that indicates that one or more (e.g., both/two) indicated TCI states (joint/DL TCI states) should be applied to the DL channel/signal being scheduled/activated/triggered. In other words, the specific field may be a field that indicates 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 referred to 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/triggered 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 states) 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.

Figures 4A-4C show other examples of application of indicated TCI states. In the example shown in Figure 4A, 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 Figure 4B, the DL DCI includes a field (TCI selection field) that indicates 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 to be applied. A code point of "01" in this field indicates that the second indicated TCI state is to be applied. A code point of "10" in this field indicates that both the first indicated TCI state and the second indicated TCI state are to be applied. A code point of "11" in this field is unused.

Figure 4C shows an example in which 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 4C).

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

The specific threshold may be, for example, at least one of an existing threshold (defined up to Rel. 15/16) and a value based on RRC parameters/UE capability information defined in Rel. 17/18 or later.

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

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

[Operation 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 specific 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 specific 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/triggered 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 second value (e.g., "01"), the UE may apply a specific 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/triggered 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 the DL channel/signal scheduled/triggered by the DCI.

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 third value (e.g., "10"), multiple indication TCI states may be applied in a first order (e.g., the first indication TCI state, then the second indication TCI state).

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

[Operation 2]
A DL channel/signal may be scheduled/triggered 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 to apply one or more indicated TCI states using higher layer signaling (RRC/MAC CE) (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 reception of 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 (options 0-2).

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

In this case, the UE may also determine 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 the existing TCI field (options 0-5).

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

(analysis)
Incidentally, in Rel. 18 and later, it is being considered to introduce a case in which a multi-TRP (e.g., a single DCI-based multi-TRP (single DCI multi-TRP)/multiple DCI-based multi-TRP (multi-DCI multi-TRP)) is configured and a unified TCI state is applied.

In Rel. 18 and later, the TCI state activation command (MAC CE) is expected to indicate whether each joint/separate (DL/UL) TCI state mapped to a TCI codepoint is the first or second joint/separate (DL/UL) TCI state (see Figure 5).

Figure 5 shows an example of TCI states mapped to TCI code points when the same (or common) indicated TCI state applies/supports for DL and UL (joint). For example, in a single DCI-based multi-TRP, one DCI (or MAC CE) may indicate one or two joint TCI states. The number of indicated TCI states may be determined based on the DCI (e.g., TCI state selection field)/RRC.

For example, a first indicated TCI state (e.g., a unified TCI state corresponding to a first TRP) and a second indicated TCI state (e.g., a unified TCI state corresponding to a second TRP) may be indicated. If the indication/application of multiple indicated TCI states corresponding to multiple (e.g., two) TRPs is supported, it is expected that the indicated TCI state applied to each TRP will be updated (or newly indicated) depending on the communication situation/communication environment.

If the indication/application of multiple indication TCI states is supported, there has been insufficient consideration given to how to control the indication/update of each indication TCI state.

If the TCI state to be applied by the UE is not sufficiently considered, the TCI state may not be applied appropriately, which could result in deterioration of communication quality, reduced throughput, etc.

The inventors therefore focused on these issues, studied operation in unified TCI states, and came up with one aspect of this embodiment.

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

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

In this disclosure, "A/B" and "at least one of A and B" may be interpreted interchangeably. 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 (or indicate), select, configure, update, and determine may be read interchangeably. In this disclosure, terms such as support, control, controllable, operate, and operateable may be read interchangeably.

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

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

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

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

In this disclosure, multi-TRP, multi-TRP system, multi-TRP transmission, and multi-PDSCH may be interpreted interchangeably.

In the present disclosure, the terms single DCI, single PDCCH, multiple TRPs based on a single DCI, activating two TCI states on at least one TCI code point, mapping at least one code point in the 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 interchangeably.

In the present disclosure, the following may be interpreted interchangeably: single TRP, channel/signal using a single TRP, 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 codepoint in the TCI field being mapped to two TCI states.

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 the present 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 interchangeably.

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

In the present disclosure, channel, signal, and channel/signal may be 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 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 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 the following embodiments of the present disclosure, 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.

(Wireless communication method)
Each embodiment of the present disclosure may be applied regardless of the setting of specific upper layer parameters, or may be applied when one or more specific upper layer parameters are set.

The specific upper layer parameter may be, for example, at least one of a parameter indicating whether a TCI selection field is present in the DL DCI (e.g., tciSelection-PresentInDCI), a parameter indicating the application of a unified TCI state (e.g., followUnifiedTCI-State), a parameter indicating the application of an indicated TCI state (e.g., applyIndicatedTCIState), and a parameter indicating whether a TCI field is present in the DL DCI (e.g., tciPresentInDCI).

Each of the following embodiments of the present disclosure may be applied to the reception of any DL channel/signal (e.g., PDSCH/PDCCH/A-CSI-RS). Each of the following embodiments of the present disclosure may be applied to the transmission of any UL channel/signal (e.g., PUSCH/PUCCH).

First Embodiment
An example of unified TCI state update control when DCI supports indication of multiple (e.g., two or more) unified TCI states for a UE is described below.

The first embodiment may be suitably applied to a single DCI-based multi-TRP. Of course, this is not limited to this, and it may also be applied to a multi-DCI-based multi-TRP or a single TRP.

One or more (e.g., two) unified TCI states may be indicated by a code point (e.g., TCI code point) in a predetermined field (e.g., TCI state field) used to indicate the TCI state included in a predetermined DCI format. The unified TCI state may mean at least one of the joint TCI state, DL TCI state, and UL TCI state. The unified TCI state indicated by the DCI may be read as the indicated TCI state. The predetermined DCI format may be a DCI format used for PDSCH scheduling (e.g., DCI format 1_1/1_2), or may be another DCI format.

If single DCI-based multi-TRP is supported/configured, one or more (e.g., two) indicated TCI states may be indicated to the UE by the codepoint in the TCI status field of one DCI.

If the same (or common) indicated TCI state applies/supports for DL and UL (joint), the DCI may indicate {first joint TCI state, second joint TCI state} to the UE. The first joint TCI state may apply to the first TRP, and the second joint TCI state may apply to the second TRP.

If separate TCI states are applied/supported for DL and UL (separate), the DCI may indicate {first DL TCI state, first UL TCI state, second DL TCI state, second UL TCI state} to the UE. The first DL TCI state and first UL TCI state may apply to the first TRP, and the second DL TCI state and second UL TCI state may apply to the second TRP.

After multiple (e.g., two) indicated TCI states have been indicated to the UE (or if the UE has multiple indicated TCI states), some of the indicated TCI states (e.g., a subset of the indicated TCI states) may be indicated to the UE.

For example, if the same (or common) indication TCI state applies/supports for DL and UL (joint), a subset (or part) of {first joint TCI state, second joint TCI state} may be indicated. If separate indication TCI states apply/supports for DL and UL (separate), a subset (or part) of {first DL TCI state, first UL TCI state, second DL TCI state, second UL TCI state} may be indicated.

For a serving cell configured with a joint DL/UL TCI mode, the network (e.g., a base station) may map the full set or a subset of {first joint TCI state, second joint TCI state} to code points in the TCI state field of a specified DCI format using a TCI state activation command (e.g., MAC CE).

For a serving cell configured with separate DL/UL TCI mode, the network (e.g., a base station) may map the full set or a subset of {first DL TCI state, first UL TCI state, second DL TCI state, second UL TCI state} to code points in the TCI state field of a specified DCI format using a TCI state activation command (e.g., MAC CE).

The UE may update the first/second indicated joint/DL/UL TCI state according to the corresponding first/second joint/DL/UL TCI state mapped to the received TCI code point. If a subset of the unified TCI state is indicated to the UE, the UE may update the newly indicated TCI state and keep other TCI states (e.g., non-indicated TCI states) without updating them.

For example, if the DCI indicates a subset (or part) of {first joint TCI state, second joint TCI state} to the UE, the UE may update the indicated joint TCI state and maintain the joint TCI state that was not indicated (e.g., the TCI state that is not updated) (see Figure 6). Figure 6 shows a case where the DCI indicates a subset (here, the first joint TCI state (TCI state #A2)) to a UE that applies/has the first joint TCI state (here, TCI state #A1) and the second joint TCI state (here, TCI state #B1). In this case, the UE may update the first joint TCI state (TCI state #A1 → TCI state #A2) and maintain the second joint TCI state.

If a subset (or part) of {first DL TCI state, first UL TCI state, second DL TCI state, second UL TCI state} is indicated to the UE, the UE may update the indicated DL/UL TCI states and maintain the non-indicated DL/UL TCI states (e.g., non-updated TCI states).

In this way, when a subset is indicated, some of the indicated TCI states are updated while other indicated TCI states are maintained, making it possible to flexibly control the updating of the indicated TCI states even when multiple indicated TCI states are supported.

The indication of a subset of unified TCI states (e.g., joint TCI states, DL/UL TCI states) may be determined based on the number of unified TCI states (or one joint TCI state, one DL/UL TCI state) mapped to the code point of the TCI state field included in the DCI. The UE may determine that a subset is indicated if only some of the TCI states (e.g., one for joint and two for separate) are mapped to the code point indicated in the TCI state field.

The indication of a subset of unified TCI states (e.g., joint TCI states, DL/UL TCI states) may be determined based on a predetermined field (e.g., TCI state selection field) included in the DCI. For example, even if the TCI state field indicates a TCI codepoint to which multiple unified TCI states (e.g., two for joint, four for separate) are mapped, if the TCI state selection field indicates only some of the TCI states, the UE may determine that a subset is indicated.

UE Operation
When a list for the unified TCI state (e.g., an upper layer parameter for the unified TCI state (dl-OrJointTCi-StattList)) is configured and has multiple (e.g., two) indicated TCI states, the UE may control the update of the indicated TCI state based on the indicated TCI state or the received TCI code point. When the UE receives a TCI codepoint to which a subset of the {first,second} indicated TCI-State(s)/{first,second} UL TCI ({first,second} TCI-UL-State(s)) is mapped, the UE may update the {first,second} indicated TCI-State(s)/{first,second} UL TCI ({first,second} TCI-UL-State(s)) and may maintain the other {first,second} indicated TCI-State(s)/{first,second} UL TCI ({first,second} TCI-UL-State(s)) that are not updated by the received TCI codepoint.

Second Embodiment
An example of unified TCI state update control will be described when multiple (eg, two or more) unified TCI state indications are supported by the MAC CE for the UE.

The second embodiment may be suitably applied when the indicated TCI state is indicated by a MAC CE. The second embodiment may be applied to at least one of a single DCI-based multi-TRP and a multi-DCI-based multi-TRP (or when multiple (e.g., two) CORESET pool indices are set). Of course, this is not limited to this, and the second embodiment may also be applied to a single TRP. The second embodiment may be applied alone or in combination with the first embodiment.

The indicated TCI state (e.g., indicated joint/DL/UL TCI state) may be indicated by the MAC CE used for activation/deactivation of the unified TCI state. For example, if a predetermined number (e.g., one) of TCI states are indicated by the MAC CE for a serving cell/TRP (e.g., one TCI state is mapped to a TCI code point by the MAC CE), the indicated TCI state may be indicated by the MAC CE.

If the same (or common) indicated TCI state applies/supports for DL and UL (joint), {first joint TCI state, second joint TCI state} may be indicated to the UE by the MAC CE for activation/deactivation of the unified TCI state. The first joint TCI state may apply to the first TRP, and the second joint TCI state may apply to the second TRP.

If separate TCI states are applied/supported for DL and UL (separate), the MAC CE for activation/deactivation of the unified TCI state may indicate {first DL TCI state, first UL TCI state, second DL TCI state, second UL TCI state} to the UE. The first DL TCI state and the first UL TCI state may apply to the first TRP, and the second DL TCI state and the second UL TCI state may apply to the second TRP.

After multiple (e.g., two) indicated TCI states have been indicated to the UE (or if the UE has multiple indicated TCI states), some of the indicated TCI states (e.g., a subset of the indicated TCI states) may be indicated to the UE by the MAC CE. The multiple (e.g., two) indicated TCI states may be indicated by the DCI or by the MAC CE.

For example, if the same (or common) indication TCI state applies/supports for DL and UL (joint), the MAC CE may indicate a subset (or part) of {first joint TCI state, second joint TCI state}. If separate indication TCI states apply/supports for DL and UL (separate), the MAC CE may indicate a subset (or part) of {first DL TCI state, first UL TCI state, second DL TCI state, second UL TCI state}.

For a serving cell configured with a joint DL/UL TCI mode, the network (e.g., a base station) may map the full set or a subset of {first joint TCI state, second joint TCI state} to code points in the TCI state field of a specified DCI format using a TCI state activation command (e.g., MAC CE).

For a serving cell configured with separate DL/UL TCI mode, the network (e.g., a base station) may map the full set or a subset of {first DL TCI state, first UL TCI state, second DL TCI state, second UL TCI state} to code points in the TCI state field of a specified DCI format using a TCI state activation command (e.g., MAC CE).

If the MAC CE indicates an indicated TCI state (e.g., if a predetermined number (e.g., one) of TCI states are activated in the MAC CE for the serving cell/TRP), the UE may update the first/second indicated joint/DL/UL TCI state based on the TCI state indicated in the MAC CE. If the UE is indicated a subset of the unified TCI state, the UE may update the newly indicated TCI state by the MAC CE and keep the other TCI states (e.g., non-indicated TCI states) without updating them (see Figure 7).

Figure 7 shows a case where a subset (here, the first joint TCI state (TCI state #A2)) is indicated by the MAC CE to a UE that applies/has a first joint TCI state (here, TCI state #A1) and a second joint TCI state (here, TCI state #B1). In this case, the UE may update the first joint TCI state (TCI state #A1 → TCI state #A2) and maintain the second joint TCI state.

In this way, when a subset is indicated, some of the indicated TCI states are updated while other indicated TCI states are maintained, making it possible to flexibly control the updating of the indicated TCI states even when multiple indicated TCI states are supported.

UE Operation
When a list for the unified TCI state (e.g., a higher layer parameter for the unified TCI state (dl-OrJointTCi-StattList)) is configured and has multiple (e.g., two) indicated TCI states, the UE may control updating of the indicated TCI state based on the TCI state indicated by the MAC CE (e.g., a TCI State Activation Command) or the received TCI codepoint. When the UE receives a TCI codepoint to which a subset of the {first,second} indicated TCI-State(s)/{first,second} UL TCI ({first,second} TCI-UL-State(s)) is mapped and a MAC CE indicating the subset, the UE may update the {first,second} indicated TCI-State(s)/{first,second} UL TCI ({first,second} TCI-UL-State(s)) and may maintain other {first,second} indicated TCI-State(s)/{first,second} UL TCI ({first,second} TCI-UL-State(s)) that are not updated by the received TCI codepoint or the MAC CE.

The MAC CE for TCI state activation may have the configuration shown in Figure 8, for example. Figure 8 may be applied to a MAC CE for activation of a unified TCI state for multi-DCI-based multi-TRP (or a unified TCI state when a CORESET pool index is set). For example, a MAC CE for unified TCI state activation/deactivation supported in Rel. 18 and later may be applied.

The CORESET pool index field included in the MAC CE may map the joint/DL/UL TCI status to the TCI codepoint in the TCI status field included in each DCI for each CORESET (or each TRP).

If the CORESET pool index is configured for any CORESET, the UE may receive {first,second} indicated TCI states ({first,second} indicated TCI-State(s))/{first,second} UL TCIs ({first,second} TCI-UL-State(s)) in the TCI codepoint via the MAC CE for unified TCI state activation/deactivation. In this case, the UE may update the {first,second} indicated TCI-State(s)/{first,second} UL TCI ({first,second} TCI-UL-State(s)) and maintain the other {first,second} indicated TCI-State(s)/{first,second} UL TCI ({first,second} TCI-UL-State(s)) that are not updated within the TCI codepoint by the MAC CE.

Third Embodiment
An example of unified TCI state update control will be described when the MAC CE supports indication of unified TCI state (eg, UL TCI/DL TCI) to the UE.

The third embodiment may be suitably applied when the indicated TCI state is indicated by the MAC CE. The third embodiment may be suitably applied when the UL TCI and DL TCI are indicated/updated by the MAC CE in a single TRP (e.g., the unified TCI state in Rel. 17). The third embodiment may be applied alone or in combination with the first embodiment/second embodiment.

The UL TCI state/DL TCI state may be indicated by the MAC CE used for activation/deactivation of the unified TCI state. For example, if separate indicated TCI states are applied/supported for DL and UL in the unified TCI state of a single TRP (separate), the MAC CE maps the UL TCI state/DL TCI state (e.g., {UL TCI, DL TCI}) to the TCI code point of the TCI state field included in the DCI.

In this case, at a certain TCI codepoint, only a part (or a subset) of the {UL TCI, DL TCI} may be updated by the MAC CE. If only some of the TCI states are indicated by the MAC CE, the TCI states indicated by the MAC CE may be updated, and the other TCI states not indicated may be controlled not to be updated (the previously indicated TCI states may be maintained).

That is, if a subset of {UL TCI, DL TCI} is indicated in the TCI codepoint, the UE updates the indicated {UL TCI, DL TCI} and maintains the other indicated {UL TCI, DL TCI} that are not updated by the MAC CE.

The MAC CE for TCI state activation may have the configuration shown in Figure 9, for example. Figure 9 may be a MAC CE for unified TCI state for a single TRP (for example, a MAC CE for unified TCI state activation/deactivation supported in Rel. 17).

<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, the UE receives any information 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.

If the above notification is made 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.

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

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

<<Notification of information from UE>>
In the above-described embodiments, notification of any information from the UE [to the NW] (in other words, transmission/reporting 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), specific signals/channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

If the above 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, any information notification from the UE in the above-described embodiments may be performed periodically, semi-persistently, or aperiodically.

<<Application of each embodiment>>
In a UE/BS, the specific process/operation/control/assumption/information(s) of at least one of the above-described embodiments may be applied (used) when one or more of the following conditions are met:
- Upper layer parameters indicating the specific processing/operation/control/assumption/information are set;
The specific process/action/control/assumption/information is determined based on relevant higher layer parameters;
The specific process/action/control/assumption/information is specified/activated/triggered by MAC CE/DCI/UCI/resource/channel/RS,
Reporting or supporting specific UE capabilities indicating (or relating to) the specific processes/actions/controls/assumptions/information;
The application of the specific process/action/control/assumption/information is determined based on specific conditions.

The specific UE capabilities may indicate at least one of the following:
Supporting the above specific processes/actions/controls/assumptions/information (e.g., updates when a subset of the indicated TCI states is indicated);
Supporting indication of a subset of the indicated TCI states;
Supporting updating of some indication TCI states based on indication of a subset of indication TCI states.

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

Furthermore, the above-mentioned specific UE capabilities may be capabilities that apply across all duplexing methods (commonly regardless of the duplexing method), or may be capabilities for each duplexing method (e.g., Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

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

(Additional Note)
The following inventions are added regarding one embodiment of the present disclosure.
[Appendix 1]
a receiver for receiving at least one of downlink control information indicating a plurality of Transmission Configuration Indication (TCI) states and a MAC Control Element (MAC CE);
a control unit that controls at least one of downlink reception and uplink transmission based on the plurality of indicated TCI states;
A terminal in which, when the control unit receives information indicating a subset of a plurality of indicated TCI states, the control unit updates some of the indicated TCI states based on the information indicating the subset, and maintains the remaining indicated TCI states.
[Appendix 2]
2. The terminal according to claim 1, wherein the information indicating the subset of the plurality of indicated TCI states is downlink control information having a code point to which the subset of the plurality of indicated TCI states is mapped.
[Appendix 3]
3. The terminal according to claim 1, wherein the information indicating the subset of the plurality of indicated TCI states is a MAC CE that maps the subset of the plurality of indicated TCI states to a code point of a TCI state field included in downlink control information.
[Appendix 4]
4. The terminal according to any one of Supplementary Note 1 to Supplementary Note 3, wherein the information indicating a subset of the plurality of indicated TCI states is a MAC CE that maps one of a TCI state for downlink and a TCI state for uplink to a code point of a TCI state field included in downlink control information.

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

FIG. 10 is a diagram showing an example of the schematic configuration of a wireless communication system according to one embodiment. Wireless communication system 1 (which may simply be referred to as system 1) may be a system that achieves 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 (for example, dual connectivity where 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 relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form a small cell C2 that is smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The location, number, shape, size, etc. of each cell and user terminal 20 are not limited to the configuration shown in the figure. Hereinafter, when base stations 11 and 12 are not to be distinguished, they will be collectively referred to as base station 10.

The wireless communication system 1 may also utilize multi-input multi-output (MIMO). For example, one cell may be formed by one antenna/base station 10, or by multiple antennas/base stations 10. One [virtual] cell (which may be called, for example, a supercell) may be made up of multiple [virtual] cells (which may be called, for example, subcells). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell with a quasi-static/dynamically changing physical range. In this case, the wireless communication system 1 may be called a cell-free system.

The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may use 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)). Macrocell 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.

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

Multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with the Common Public Radio Interface (CPRI), X2/Xn interface, etc.) or wirelessly (e.g., NR communication). For example, if 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 the relay station (relay), may be called an IAB node.

A base station 10 may be connected to the core network 30 directly or via another base station 10. The core network 30 may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), 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 a single network node. Communication with an external network (e.g., the Internet) may also 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. Note that 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 as the UL and DL radio access methods.

In the wireless communication system 1, the downlink channel may be 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)), or the like.

Furthermore, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), 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 via the PDCCH. The lower layer control information may include, for example, Downlink Control Information (DCI) including scheduling information for at least one of the PDSCH and PUSCH.

Note that the DCI that schedules the PDSCH may be referred to as a DL assignment or DL DCI, and the DCI that schedules the PUSCH may be referred to as 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 (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 area and search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.

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

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

Note that in this disclosure, downlink, uplink, etc. may be expressed without the word "link." Also, various channels may be expressed without the word "Physical" at 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 the PBCH) may be referred to as an SS/PBCH block, an SS block (SSB), etc. Note that SS, SSB, etc. may also be referred to as a reference signal.

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

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

Note that this example mainly shows the functional blocks that characterize the present embodiment, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field 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 also control transmission and reception using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140, measurements, 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 also perform call processing of communication channels (setting up, releasing, 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 common understanding in the technical field to which this disclosure relates.

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

The transmitting and receiving antenna 130 can be composed of 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 also receive the above-mentioned uplink channel, uplink reference signal, etc.

The transceiver unit 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, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

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

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 unit 120 (reception processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, thereby acquiring user data, etc.

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 by at least one of the transmitter/receiver 120, the transmitter/receiver antenna 130, and the transmission path interface 140.

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

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

The transceiver unit 120 may transmit at least one of downlink control information and MAC control elements (MAC CEs) indicating multiple Transmission Configuration Indication (TCI) states.

The control unit 110 may control at least one of downlink reception and uplink transmission based on the multiple indicated TCI states. When the control unit 110 transmits information indicating a subset of the multiple indicated TCI states, the control unit 110 may update some of the multiple indicated TCI states and maintain the remaining indicated TCI states.

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

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

The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, a control circuit, etc., as described based on 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 also control transmission and reception, measurement, etc. using the transmission and reception unit 220 and the transmission and reception antenna 230. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals and transfer them to the transmission and reception 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 common understanding in the technical field related to this disclosure.

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

The transmitting and 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 unit 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver unit 220 may also transmit the above-mentioned uplink channel, uplink reference signal, etc.

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

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

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

Whether or not to apply DFT processing may be based on the settings for transform precoding. If transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform; if not, it may not be necessary to perform DFT processing as the 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 unit 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.

The transceiver unit 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 also 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 also be referred to as 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 interchangeable.

Note that the transmitter and receiver of the user terminal 20 in this disclosure may be configured by at least one of the transmitter/receiver 220 and the transmitter/receiver antenna 230.

The transceiver unit 220 may receive at least one of downlink control information and MAC control elements (MAC CEs) indicating multiple Transmission Configuration Indication (TCI) states.

The control unit 210 may control at least one of downlink reception and uplink transmission based on the multiple indicated TCI states. When the control unit 210 receives information indicating a subset of the multiple indicated TCI states, the control unit 210 may update some of the indicated TCI states based on the information indicating the subset, and may control the remaining indicated TCI states to be maintained.

The information indicating a subset of the multiple indicated TCI states may be downlink control information having a code point to which the subset of the multiple indicated TCI states is mapped.

The information indicating a subset of the multiple indicated TCI states may be a MAC CE that maps the subset of the multiple indicated TCI states to a code point in the TCI state field included in the downlink control information.

The information indicating a subset of multiple indicated TCI states may be a MAC CE that maps one of the downlink TCI state and the uplink TCI state to a code point in the TCI state field included in the downlink control information.

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

Here, functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission functions may be called a transmitting unit, transmitter, etc. As mentioned above, there are no particular limitations on how these functions are implemented.

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. Figure 13 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, memory 1002, storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

In this disclosure, terms such as apparatus, circuit, device, section, and unit may be used interchangeably. The hardware configuration of the base station 10 and 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 a single 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 reading and writing data from and to 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) that includes an interface with peripheral devices, a control unit, an arithmetic unit, registers, etc. For example, at least a portion of the above-mentioned control unit 110 (210), transceiver unit 120 (220), etc. may be realized by the processor 1001.

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

Memory 1002 is a computer-readable recording medium and may be composed of, for example, at least one of Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. Memory 1002 may also be referred to as a register, cache, main memory, etc. Memory 1002 can store executable programs (program code), 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 disc (Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.

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 referred to as a network device, network controller, network card, or communication module. The communication device 1004 may be configured to include high-frequency switches, duplexers, filters, frequency synthesizers, etc. to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitter/receiver unit 120 (220), transmitter/receiver antenna 130 (230), etc. may be implemented by the communication device 1004. The transmitter/receiver unit 120 (220) may be implemented as a transmitter unit 120a (220a) and a receiver unit 120b (220b) that are physically or logically separated.

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

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

In addition, devices included in the core network 30 (e.g., network nodes that provide NF) may also be realized using the above-mentioned functional block/hardware configuration.

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

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, numerology may be a communication parameter applied to at least one of the transmission and reception of a signal or channel. 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 structure, specific filtering processing performed by the transmitter/receiver in the frequency domain, and specific windowing processing performed by the transmitter/receiver in the time domain.

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

A slot may include multiple minislots. Each minislot may consist of one or more 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.

Radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals. Radio frame, subframe, slot, minislot, and symbol may each be referred to by a different name. Note that the time units used in this disclosure, such as frame, subframe, slot, minislot, and symbol, may be interchangeable.

For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. In other words, at least one of a subframe and a TTI may be a subframe (1 ms) as in existing LTE, or may be a period shorter than 1 ms (e.g., 1-13 symbols), or may be a period longer than 1 ms. Note that the unit representing a 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 performs scheduling to allocate radio resources (such as the frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. However, the definition of TTI is not limited to this.

The TTI may be a transmission time unit for a channel-encoded data packet (transport block), code block, code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., number of symbols) to which a transport block, code block, 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 smallest time unit for scheduling. Furthermore, the number of slots (minislots) that make up the smallest time unit for scheduling may be controlled.

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

Note that a long TTI (e.g., a normal TTI, 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 of 1 ms or more but less than the TTI length of a long TTI.

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 also 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.

Note that one or more RBs may also be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

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

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. Here, the common RBs may be identified by the index of the RB relative to the common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

BWPs may include UL BWPs (BWPs for UL) and DL BWPs (BWPs 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 structures of the radio frames, subframes, slots, minislots, and symbols described above 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, symbol length, and cyclic prefix (CP) length can be changed in various ways.

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

The names used for parameters and the like in this disclosure are not limiting in any way. Furthermore, the mathematical 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 way.

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

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 and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added to. Output information, signals, etc. may be deleted. Input information, signals, etc. may be sent to another device.

With regard to any information (e.g., variables, constants, parameters) described in this disclosure, even if not specifically stated in the above embodiments, any first device (e.g., UE/base station) may notify any second device (e.g., base station/UE) of information indicating/identifying (or relating to) the value of that information.

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 using 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.

Note that physical layer signaling may also be referred to as Layer 1/Layer 2 (L1/L2) control information (L1/L2 control signal), L1 control information (L1 control signal), etc. Furthermore, RRC signaling may also be referred to as RRC messages, such as RRC Connection Setup messages or RRC Connection Reconfiguration messages. Furthermore, MAC signaling may also be notified using, for example, MAC Control Elements (CEs).

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

The determination may be made based on a value represented by a single bit (0 or 1), a Boolean value represented as true or false, or a comparison of numerical values (for example, a comparison 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.

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

As used in this disclosure, the terms "system" and "network" may be used interchangeably. "Network" may refer to 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 term "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 term "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 transmit 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 read as interchangeable terms.

Furthermore, in this disclosure, terms such as TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, and joint TCI state may be interpreted interchangeably.

Furthermore, in this disclosure, terms such as "QCL," "QCL assumptions," "QCL relationships," "QCL type information," "QCL properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL types (e.g., Type A, Type D)" may be read interchangeably.

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

Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and 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," and "Component Carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

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 be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms "cell" or "sector" refer to part or all of the coverage area of at least one of the base station and base station subsystems that provide communication services within this coverage area.

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 that 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 referred to as 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 mobile body in question refers to an object that can move at any speed, and of course also includes cases where the mobile body is stationary. Examples of the mobile body in question include, but are 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, satellites, drones, multicopters, quadcopters, balloons, and objects mounted on these. The mobile body in question may also be a mobile body that moves autonomously based on operation commands.

The moving object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving object (e.g., a drone, a self-driving car, 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. 14 is a diagram showing an example of a vehicle according to one 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, for example, at least one of an engine, a motor, or a hybrid of an engine and a motor. The steering unit 42 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by 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 for the front wheels 46/rear wheels 47 obtained by a rotation speed sensor 51, an air pressure signal for the front wheels 46/rear wheels 47 obtained by an air pressure sensor 52, a vehicle speed signal obtained by a vehicle speed sensor 53, an acceleration signal obtained by an acceleration sensor 54, a depression amount signal for the accelerator pedal 43 obtained by an accelerator pedal sensor 55, a depression amount signal for the brake pedal 44 obtained by a brake pedal sensor 56, an operation signal for the shift lever 45 obtained by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 58.

The information service unit 59 is composed of various devices, such as a car navigation system, audio system, speakers, displays, televisions, and radios, that provide (output) various information such as driving information, traffic information, and entertainment information, as well as one or more ECUs that control these devices. The information service unit 59 uses information obtained 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., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

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

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, all of which 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 external devices. For example, it sends and receives various information to and from external devices via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or user terminal 20 described above. The communication module 60 may also be, for example, at least one of the base station 10 and user terminal 20 described above (or may function as at least one of the base station 10 and user terminal 20).

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

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

Furthermore, the communication module 60 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 other components provided on the vehicle 40.

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

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

In this disclosure, operations described as being performed by a base station may in some cases also be performed by its upper node. In a network including 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 thereof.

Each aspect/embodiment described in this disclosure may be used alone, in combination, or switched between depending on the implementation. Furthermore, the processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in this disclosure may be rearranged as long as they are consistent. For example, the methods described in this disclosure present various step elements in an exemplary order, and are not limited to the specific order presented.

Each aspect/embodiment described in this disclosure may be applied to any of the following mobile communication systems: Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or decimal number)), Future Radio Access (FRA), New-Radio 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), or other appropriate wireless communication methods, as well as next-generation systems that are extended, modified, created, or defined based on these. It may also be applied to a combination of multiple systems (for example, a combination of LTE or LTE-A with 5G).

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."

As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

As used in this disclosure, the term "determining" 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., searching in a table, database, or other data structure), ascertaining, etc.

Furthermore, "determination" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.

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 read interchangeably with the above-mentioned actions.

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 interchangeably read as "be expected." For example, "expect(s)..." ("..." may be expressed, for example, as a that clause, a to-infinitive, etc.) may be interchangeably read as "be expected..." or "does... (if the above "..." is a to-infinitive, a verb with "to")." "does not expect..." may be interchangeably read as "be not expected..." or "does not... (if the above "..." is a to-infinitive, a verb with "to")." Furthermore, "An apparatus A is not expected..." may be interchangeably read as "apparatus B other than apparatus A does not expect..." from apparatus A (for example, if apparatus A is a UE, apparatus B may be a base station).

The term "maximum transmit power" used in this disclosure may refer to 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," "coupled," or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

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

In this disclosure, the term "A and B are different" may mean "A and B are different from each other." Note that this 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." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

In this disclosure, where articles are added by translation, such as a, an, and the in English, this disclosure may include the noun following these articles being plural.

In this disclosure, terms such as "less than or equal to," "less than," "greater than," "more than," "equal to," etc. may be read interchangeably. Furthermore, in this disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be read interchangeably, not limited to the positive, comparative, and superlative. Furthermore, in this disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be read interchangeably, not limited to the positive, comparative, and superlative, as expressions with the prefix "i-th" (i is any integer) (for example, "highest" may be read interchangeably as "i-th highest").

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

In the present disclosure, expressions such as "when A, B," "if A, (then) B," "B upon A," "B in response to A," "B based on A," "B during/while A," "B before A," "B at (the same time as)/on A," "B after A," "B since A," and "B until A" may be interchangeable. Note that A and B may be replaced with other appropriate expressions, such as nouns, gerunds, and regular sentences, depending on the context. The time difference between A and B may be nearly zero (immediately after or immediately before). A time offset may also be applied to the time at which A occurs. For example, "A" may be interpreted 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 determined by the UE based on signaled information.

In the present disclosure, terms such as timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, and resource may be interpreted interchangeably.

Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The description of the present disclosure is for illustrative purposes only and does not impose any limiting meaning on the invention according to the present disclosure.

Claims (6)

a receiver for receiving at least one of downlink control information indicating a plurality of Transmission Configuration Indication (TCI) states and a MAC Control Element (MAC CE);
a control unit that controls at least one of downlink reception and uplink transmission based on the plurality of indicated TCI states;
A terminal in which, when the control unit receives information indicating a subset of a plurality of indicated TCI states, the control unit updates some of the indicated TCI states based on the information indicating the subset, and maintains the remaining indicated TCI states. The terminal according to claim 1, wherein the information indicating the subset of the plurality of indicated TCI states is downlink control information having a code point to which the subset of the plurality of indicated TCI states is mapped. The terminal according to claim 1, wherein the information indicating the subset of the multiple indicated TCI states is a MAC CE that maps the subset of the multiple indicated TCI states to a code point in a TCI state field included in downlink control information. The terminal according to claim 1, wherein the information indicating a subset of the multiple indicated TCI states is a MAC CE that maps one of the downlink TCI state and the uplink TCI state to a code point in the TCI state field included in the downlink control information. receiving at least one of downlink control information and a MAC Control Element (MAC CE) indicating a plurality of Transmission Configuration Indication (TCI) states;
and controlling at least one of downlink reception and uplink transmission based on the plurality of indicated TCI states;
A wireless communication method for a terminal, which, when receiving information indicating a subset of a plurality of indicated TCI states, updates some of the indicated TCI states based on the information indicating the subset, and maintains the remaining indicated TCI states. a transmitter for transmitting at least one of downlink control information and a MAC Control Element (MAC CE) indicating a plurality of Transmission Configuration Indication (TCI) states;
a control unit that controls at least one of downlink reception and uplink transmission based on the plurality of indicated TCI states;
A base station, wherein when the control unit transmits information indicating a subset of a plurality of indicated TCI states, the control unit updates some of the indicated TCI states and maintains the remaining indicated TCI states.