JP7622068B2 - Terminal, wireless communication method, base station and system - Google Patents

Description

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

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

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

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

In NR, the use of the UL transmission configuration indication state (Transmission Configuration Indication state (TCI state)) is being considered as a beam (precoder) indication method for the uplink (UL).

However, there is still no research on how to control the UL beam used by the UE when the UL TCI state is introduced. If this control is not clarified, there is a risk that the increase in communication throughput will be suppressed.

Therefore, an object of the present disclosure is to provide a terminal, a wireless communication method , a base station , and a system that can appropriately control PUSCH transmission.

A terminal according to one aspect of the present disclosure includes a receiver that receives a MAC Control Element (MAC CE) that activates one or more TCI states used for a downlink shared channel (PDSCH), a downlink control channel (PDCCH), and a channel state information reference signal (CSI-RS), and an uplink shared channel (PUSCH) from a Transmission Configuration Indication state (TCI state) list, and receives downlink control information (DCI); a controller that determines a TCI state from among the one or more TCI states based on a specific field included in the DCI; and a transmitter that applies a spatial domain filter determined based on the TCI state to transmit a non-codebook-based uplink shared channel.

According to one aspect of the present disclosure, PUSCH transmission can be appropriately controlled.

FIG. 1 is a diagram illustrating an example of a correspondence relationship between the number of antenna ports field and the number of antenna ports in the first embodiment. FIG. 2 is a diagram illustrating an example of a transmission scheme setting for enabling the control of the first embodiment. FIG. 3 shows table 7.3.1.1.2-29 described in TS 38.212 V16.2.0. 4A and 4B are diagrams illustrating an example of a table related to spatial relationship information indication according to the second embodiment. 5A and 5B are diagrams illustrating an example of a table related to spatial relationship information indication according to the second embodiment. FIG. 6 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 7 is a diagram illustrating an example of the configuration of a base station according to an embodiment. FIG. 8 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. FIG. 9 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment.

(TCI, spatial relations, QCL)
In NR, it is considered that the UE controls 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) of at least one of a signal and a channel (which may be expressed as signal/channel. In this disclosure, "A/B" may also be read as "at least one of A and B") based on a transmission configuration indication state (TCI state).

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

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

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

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

A plurality of types (QCL types) of QCL may be defined. For example, four QCL types A to D may be provided, each of which has different parameters (or parameter sets) that can be assumed to be the same. The parameters (which may be called QCL parameters) are as follows:
QCL Type A: Doppler shift, Doppler spread, mean delay and delay spread,
QCL Type B: Doppler shift and Doppler spread,
QCL Type C: Doppler shift and mean delay,
QCL Type D: Spatial reception parameters.

Types A to C may correspond to QCL information related to synchronization processing of at least one of time and frequency, and type D may correspond to QCL information related to beam control.

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

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

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

In the present disclosure, higher layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof.

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

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

In addition, the channel/signal to which the TCI state applies may be referred to as a target channel/reference signal (target channel/RS) or simply as a target, and the other signal may be referred to as a reference reference signal (reference RS), source RS, or simply as a reference.

The channel for which the TCI state is set (specified) may be, for example, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc.

In addition, the RS (DL-RS) that has a QCL relationship with the channel may be, for example, at least one of a Synchronization Signal Block (SSB) and a Channel State Information Reference Signal (CSI-RS). Alternatively, the DL-RS may be a CSI-RS (also called a Tracking Reference Signal (TRS)) used for tracking, or a reference signal (also called a QRS) used for QCL detection.

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.

The TCI state information element (RRC's "TCI-state IE") set by higher layer signaling may include one or more QCL information ("QCL-Info"). The QCL information may include at least one of information on the DL-RS that is in a QCL relationship (DL-RS relationship information) and information indicating the QCL type (QCL type information). The DL-RS relationship information may include information such as the index of the DL-RS (e.g., SSB index, Non-Zero-Power (NZP) CSI-RS resource identifier), the index of the cell in which the RS is located, and the index of the Bandwidth Part (BWP) in which the RS is located.

(Spatial Relationship for SRS, PUSCH)
In Rel. 15 NR, the UE may receive information (SRS configuration information, e.g., parameters in the RRC control element "SRS-Config") used to transmit a measurement reference signal (e.g., a Sounding Reference Signal (SRS)).

Specifically, the UE may receive at least one of information regarding one or more SRS resource sets (SRS resource set information, e.g., the RRC control element "SRS-ResourceSet") and information regarding one or more SRS resources (SRS resource information, e.g., the RRC control element "SRS-Resource").

An SRS resource set may relate to (group) a number of SRS resources, each of which may be identified by an SRS Resource Indicator (SRI) or SRS Resource Identifier (ID).

The SRS resource set information may include an SRS resource set ID (SRS-ResourceSetId), a list of SRS resource IDs (SRS-ResourceId) used in the resource set, an SRS resource type, and information on SRS usage.

Here, the SRS resource type may indicate any of periodic SRS (Periodic SRS (P-SRS)), semi-persistent SRS (Semi-Persistent SRS (SP-SRS)), and aperiodic CSI (Aperiodic SRS (A-SRS)). Note that the UE may transmit P-SRS and SP-SRS periodically (or periodically after activation) and transmit A-SRS based on an SRS request in the DCI.

In addition, the usage (RRC parameter "usage", L1 (Layer-1) parameter "SRS-SetUse") may be, for example, beam management, codebook (CB), noncodebook (NCB), antenna switching, etc. The SRS for codebook or noncodebook usage may be used to determine a precoder for codebook-based or noncodebook-based uplink shared channel (Physical Uplink Shared Channel (PUSCH)) transmission based on the SRI.

For example, the UE may determine a precoder for PUSCH transmission based on the SRI, a Transmitted Rank Indicator (TRI), and a Transmitted Precoding Matrix Indicator (TPMI) in case of codebook-based transmission. The UE may determine a precoder for PUSCH transmission based on the SRI in case of non-codebook-based transmission.

The SRS resource information may include an SRS resource ID (SRS-ResourceId), an SRS port number, an SRS port number, a transmission Comb, an SRS resource mapping (e.g., time and/or frequency resource position, resource offset, resource period, number of repetitions, number of SRS symbols, SRS bandwidth, etc.), hopping related information, an SRS resource type, a sequence ID, spatial relationship information of the SRS, etc.

The spatial relationship information of the SRS (e.g., the RRC information element "spatialRelationInfo") may indicate spatial relationship information between a predetermined reference signal and the SRS. The predetermined reference signal may be at least one of a Synchronization Signal/Physical Broadcast Channel (SS/PBCH) block, a Channel State Information Reference Signal (CSI-RS), and an SRS (e.g., another SRS). The SS/PBCH block may be referred to as a Synchronization Signal Block (SSB).

The spatial relationship information of the SRS may include at least one of an SSB index, a CSI-RS resource ID, and an SRS resource ID as an index of the above-mentioned specified reference signal.

In the present disclosure, the SSB index, SSB resource ID, and SSB Resource Indicator (SSBRI) may be interchangeable. Also, the CSI-RS index, CSI-RS resource ID, and CSI-RS Resource Indicator (CRI) may be interchangeable. Also, the SRS index, SRS resource ID, and SRI may be interchangeable.

The spatial relationship information of the SRS may include a serving cell index, a BWP index (BWP ID), etc. corresponding to the above-mentioned specified reference signal.

When spatial relationship information regarding the SSB or CSI-RS and the SRS is configured for a certain SRS resource, the UE may transmit the SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter (spatial domain receive filter) for receiving the SSB or CSI-RS. In this case, the UE may assume that the UE receive beam for the SSB or CSI-RS and the UE transmit beam for the SRS are the same.

When spatial relationship information regarding a certain SRS (target SRS) resource is configured between another SRS (reference SRS) and the SRS (target SRS), the UE may transmit the target SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter (spatial domain transmit filter) for transmitting the reference SRS. In other words, in this case, the UE may assume that the UE transmit beam of the reference SRS and the UE transmit beam of the target SRS are the same.

The UE may determine the spatial relationship of the PUSCH scheduled by the DCI (e.g., DCI format 0_1) based on the value of a predetermined field (e.g., an SRS resource identifier (SRI) field) in the DCI. Specifically, the UE may use spatial relationship information of the SRS resource (e.g., the RRC information element "spatialRelationInfo") determined based on the value of the predetermined field (e.g., SRI) for PUSCH transmission.

In Rel. 15/16 NR, when using codebook-based transmission for PUSCH, the UE is configured by RRC with a codebook-use SRS resource set having up to two SRS resources, and one of the up to two SRS resources may be indicated by DCI (1-bit SRI field). The transmission beam for PUSCH is specified by the SRI field.

The UE may determine the TPMI and number of layers (transmission rank) for the PUSCH based on the precoding information and number of layers field (hereinafter also referred to as the precoding information field). The UE may select a precoder based on the TPMI, number of layers, etc. from the uplink codebook for the same number of ports as the number of SRS ports indicated by the upper layer parameter "nrofSRS-Ports" set for the SRS resource specified by the SRI field.

In Rel. 15/16 NR, when non-codebook-based transmission is used for PUSCH, the UE is configured by RRC with a non-codebook-used SRS resource set having up to four SRS resources, and one or more of the up to four SRS resources may be indicated by DCI (2-bit SRI field).

The UE may determine the number of layers (transmission rank) for the PUSCH based on the SRI field. For example, the UE may determine that the number of SRS resources specified by the SRI field is the same as the number of layers for the PUSCH. The UE may also calculate a precoder for the SRS resources.

If a CSI-RS (which may be called associated CSI-RS) associated with the SRS resource (or the SRS resource set to which the SRS resource belongs) is configured by a higher layer, the transmission beam of the PUSCH may be calculated based on (measurement of) the configured associated CSI-RS. Otherwise, the transmission beam of the PUSCH may be specified by the SRI.

In addition, the UE may be configured to use codebook-based PUSCH transmission or non-codebook-based PUSCH transmission by a higher layer parameter "txConfig" indicating a transmission scheme. The parameter may indicate a value of "codebook" or "nonCodebook".

In this disclosure, codebook-based PUSCH (codebook-based PUSCH transmission, codebook-based transmission) may refer to PUSCH when the UE is configured with "codebook" as the transmission scheme. In this disclosure, non-codebook-based PUSCH (non-codebook-based PUSCH transmission, non-codebook-based transmission) may refer to PUSCH when the UE is configured with "non-codebook" as the transmission scheme.

(UL TCI state)
In NR, the use of the UL TCI state as a beam indication method for UL is being considered. The UL TCI state is similar to the notification of the UE's DL beam (DL TCI state). Note that the DL TCI state may be read as the TCI state for PDCCH / PDSCH and vice versa.

The UL TCI state may be configured in the UE by spatial relation information specified in a particular release (e.g., spatialRelationInfo-r17 specified in Rel. 17) (which may also be referred to as UL TCI state information). The UL TCI state may also be referred to as the unified TCI state (U-TCI state), spatial relation, release-specific spatial relation, etc.

One or more of the configured UL TCI states may be activated/deactivated using a MAC CE. Also, spatial relationship information for at least one of the A-SRS, PUSCH, PUCCH, and PRACH from the configured/activated UL TCI states may be specified to the UE by the DCI.

The channel/signal (which may be referred to as a target channel/RS) for which the UL TCI state is set (specified) may be, for example, at least one of a PUSCH, a demodulation reference signal (DMRS) for the PUSCH, a PUCCH, a DMRS for the PUCCH, a random access channel (Physical Random Access Channel (PRACH)), an SRS, etc.

In addition, the RS (reference RS) that has a QCL relationship with the channel/signal may be, for example, a DL RS (e.g., SSB, CSI-RS, TRS, etc.) or a UL RS (e.g., SRS, SRS for beam management, etc.).

In the UL TCI state, an RS that has a QCL relationship with the channel/signal may be associated with a panel (panel ID) for receiving or transmitting the RS. The association may be explicitly set (or specified) or implicitly determined by higher layer signaling (e.g., RRC signaling, MAC CE, etc.).

The correspondence between the RS and the panel ID may be set by being included in the UL TCI status information, or may be set by being included in at least one of the resource setting information, spatial relationship information, etc. of the RS.

The QCL type indicated by the UL TCI status may be an existing QCL type A-D or may be another QCL type and may include a predefined spatial relationship, associated antenna ports (port index), etc.

When a UE is assigned an associated Panel ID for a UL transmission (e.g., assigned by a DCI), the UE may perform the UL transmission using a panel corresponding to the Panel ID. The Panel ID may be associated with a UL TCI state, and when a UL TCI state is assigned (or activated) for a given UL channel/signal, the UE may identify the panel to use for the UL channel/signal transmission according to the Panel ID associated with the UL TCI state.

However, there is still no research on how to control the UL beam used by the UE when the UL TCI state is introduced. If this control is not clarified, there is a risk that the increase in communication throughput will be suppressed.

For example, when the UL TCI state is introduced, for the above-mentioned codebook-based PUSCH, if SSB/CSI-RS is used as a reference signal for PUSCH transmission, it is possible not to set the SRS with usage = codebook. In this case, it is possible that the base station determines the TPMI, transmission rank, etc. based on the DL CSI measurement (feedback report) by the UE, rather than the SRS measurement.

In this case, there is no need to include an SRI field in the DCI format, but no consideration has been given to how to notify QCL (spatial relationship) information, number of antenna ports, etc. for PUSH when the SRI field is not used.

Therefore, the inventors have come up with a method for appropriately transmitting PUSH, taking into account the case where the UL TCI state is introduced.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. The wireless communication methods according to the embodiments may be applied alone or in combination. The embodiments of the present disclosure may be used in cases where the UL TCI state is not introduced.

In addition, in this disclosure, "A/B" may also mean "at least one of A and B."

In this disclosure, the terms activate, deactivate, indicate, select, configure, update, determine, etc. may be interpreted as interchangeable.

In the present disclosure, the terms panel, beam, panel group, beam group, Uplink (UL) transmitting entity, TRP, spatial relationship information (SRI), spatial relationship, control resource set (COntrol REsource SET (CORESET)), Physical Downlink Shared Channel (PDSCH), codeword, base station, predetermined antenna port (e.g., DeModulation Reference Signal (DMRS) port), predetermined antenna port group (e.g., DMRS port group), predetermined group (e.g., Code Division Multiplexing (CDM) group, predetermined reference signal group, CORESET group), predetermined resource (e.g., predetermined reference signal resource), predetermined resource set (e.g., predetermined reference signal resource set), CORESET pool, PUCCH group (PUCCH resource group), spatial relationship group, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state state), QCL, etc. may be read as interchangeable.

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

In the present disclosure, the terms index, ID, indicator, and resource ID may be interchangeable. Also, in the present disclosure, the terms sequence, list, set, group, cluster, subset, and the like may be interchangeable.

In the following embodiments, spatial relationship information (spatialRelationInfo), spatial relationship information specified in a particular release (e.g., spatialRelationInfo-r17 specified in Rel. 17), TCI state specified in a particular release (e.g., TCIstate-r17 specified in Rel. 17), etc. may be read as interchangeable.

In addition, in the following embodiments, the spatial relationship information ID (spatialRelationInfoId), the spatial relationship information ID defined in a particular release (e.g., spatialRelationInfoId-r17 defined in Rel. 17), the TCI state ID defined in a particular release (e.g., TCIstateId-r17 defined in Rel. 17), etc. may be read as interchangeable. Note that the names of these parameters are not limited to these.

In the description of the following embodiments, "Spatial Relation Information (SRI)", "spatial relation information for PUSCH", "spatial relation", "UL beam", "UE transmission beam", "UL TCI", "UL TCI state", "spatial relation of UL TCI state", SRS Resource Indicator (SRI), SRS resource, precoder, etc. may be interchangeable.

(Wireless communication method)
First Embodiment
The first embodiment relates to a codebook-based PUSCH when utilizing the U-TCI framework.

DCI Fields for Specifying Spatial Relationship Information
The UE may determine (select) the UL TCI of the PUSCH based on some or all of a specific field included in the DCI. The specific field may be a new field (e.g., a UL beam field, a UL TCI field, etc.) that is not included in the existing Rel. 15 NR DCI format, or a field (e.g., an SRI field, an SRS request field, a precoding information field, etc.) that is included in the existing Rel. 15 NR DCI format.

The UE may determine the UL TCI of the PUSH based on the above-mentioned specific fields included in the DCI from one or more spatial relationship information (higher layer parameter "spatialRelationInfo") set or activated by higher layer signaling (e.g., RRC signaling, MAC signaling).

The UE may configure the list of spatial relationship information by RRC signaling. The UE may activate one or more pieces of spatial relationship information from the configured list of spatial relationship information by MAC CE.

The value of the specific field included in the DCI may correspond to at least one of the following: a spatial relationship information ID associated with the spatial relationship information (e.g., the upper layer parameter "spatialRelationInfoId"), an entry number in the list (e.g., if the list includes n pieces of spatial relationship information, the entry numbers are from 0 to n-1), an index of the activated spatial relationship information (the first active spatial relationship information has index 0, the second active spatial relationship information has index 1, ...).

The spatial relationship information may include information regarding a reference reference signal (e.g., SSB/CSI-RS/SRS). The UE may transmit a PUSCH according to the spatial relationship with respect to the reference reference signal.

In the first embodiment, the DCI including the specific field (e.g., the UL TCI field) may not include the SRI field. In other words, in a DCI format that schedules a PUSCH, the specific field may be included instead of the SRI field.

[Setting/Specifying Number of Antenna Ports]
The UE may determine the TPMI (or precoder) and the RI (or number of layers) based on the precoding information field. The UE may select a precoder from a codebook for the uplink.

The number of antenna ports for the codebook (e.g., for referencing the codebook) may be configured in the UE by higher layer signaling (e.g., the RRC information element "PUSCH-Config" for PUSCH configuration) or may be indicated to the UE by a DCI field (e.g., the number of antenna ports field). Note that the codepoint of the number of antenna ports field may be mapped to 1, 2, 4, or any other number of supported antenna ports.

The number of antenna ports for the codebook does not depend on the number of antenna ports for the SRS resource (e.g., given by the higher layer parameter "nrofSRS-Ports"). In other words, the number of antenna ports for the codebook may be notified to the UE by a higher layer parameter different from the higher layer parameter of the number of antenna ports for the SRS resource, or by the number of antenna ports field.

The UE may select a precoder from an uplink codebook for the configured or specified number of antenna ports based on the above TPMI, number of layers, etc.

The UE may transmit the PUSH using the configured or specified number of antenna ports.

Figure 1 is a diagram showing an example of the correspondence between the antenna port number field and the number of antenna ports in the first embodiment. In this example, for example, the values 0, 1, and 2 in the antenna port number field correspond to a single port (number of ports 1), two ports (number of ports 2), and four ports (number of ports 4), respectively.

The correspondence may be predefined by a specification, may be set by higher layer signaling, may be specified by DCI, or may be determined based on UE capabilities.

The above-mentioned configuration/designation of the number of antenna ports may be applied only if any of the following conditions are met:
The spatial relationship information specified by the specific fields mentioned above includes information regarding the reference DL reference signal (e.g., SSB/CSI-RS);
- The spatial relationship information specified by the specific fields mentioned above includes information regarding the reference UL reference signal (e.g., SRS).

In addition, when the spatial relationship information specified by the above-mentioned specific field includes information regarding a reference UL reference signal, the number of antenna ports may be determined by the number of antenna ports set for the reference UL reference signal (e.g., the number of antenna ports for SRS resources included in the RRC information element "SRS-Config" for SRS configuration) (in this case, the above-mentioned setting/instruction of the number of antenna ports may not be applied).

In addition, when the spatial relationship information specified by the above-mentioned specific field includes information regarding a reference DL reference signal, an existing Rel. 15/16 table showing the correspondence between the precoding information field and the TPMI and number of layers may be referenced, or a table showing a new correspondence may be referenced.

If the DCI includes the above-mentioned antenna port number field, the precoding information field may be used to indicate the TPMI and the number of layers. However, the precoding information field in this case may be fixed to X bits (e.g., X=6). The UE may assume that the precoding information field has a fixed size, regardless of the value of the antenna port number field (the number of antenna ports indicated by the antenna port number field).

In the existing NR specifications, in the case of codebook-based transmission, the size of the precoding information field is variable based on the number of antenna ports that is set semi-statically (for example, the same number of ports as the number of SRS ports indicated by the upper layer parameter "nrofSRS-Ports"). On the other hand, when the number of antenna ports is dynamically specified by the antenna port number field, a fixed size of the precoding information field is preferable (because if the size of the DCI changes dynamically, it becomes difficult to perform decoding properly).

The value of X may be predefined by a specification, may be set by higher layer signaling, or may be determined based on UE capabilities.

[Transmission scheme]
A transmission scheme for enabling the control of the first embodiment may be newly defined. Fig. 2 is a diagram showing an example of the setting of a transmission scheme for enabling the control of the first embodiment. This example is described using Abstract Syntax Notation One (ASN.1) notation (note that this is merely an example and may not be a complete description).

In this example, the PUSCH configuration information (PUSCH-Config) may include a new parameter (txConfig-r17) indicating a transmission scheme instead of the existing parameter (txConfig) indicating a transmission scheme. The new parameter may take a value of "newTxScheme" in addition to the existing "codebook" and "nonCodebook". A UE in which the new parameter "newTxScheme" is set may enable the control of the first embodiment (e.g., the UE may expect that the spatial relationship information specified for the PUSCH includes CSI-RS/SSB as a reference signal in addition to or instead of SRS).

Note that the names of the above new parameters (txConfig-r17) and the new transmission scheme (newTxScheme) are not limited to these. For example, "new transmission scheme (newTxScheme)" may be read as "new transmission scheme for codebook (newTxSchemeForCodebook)," which indicates a new transmission scheme for the codebook.

According to the first embodiment described above, the UE can appropriately determine the UL TCI for the codebook-based PUSCH. Note that the first embodiment may also be applied to non-codebook-based transmission.

Second Embodiment
The second embodiment relates to a non-codebook based PUSCH when using the U-TCI framework.

The UE may determine (select) the UL TCI of the PUSCH based on some or all of the specific fields included in the DCI. The specific fields may be new fields (e.g., UL beam fields, UL TCI fields, etc.) that are not included in the DCI format of the existing Rel. 15 NR, or may be fields (e.g., SRI fields, SRS request fields, precoding information fields, etc.) that are included in the DCI format of the existing Rel. 15 NR.

If the particular field is an SRI field, the SRI field may be mapped to an SRS resource with usage=non-codebook. In this case, the UE may not expect the DCI to include the new field (e.g., the UL TCI field). For simplicity, the new field is hereinafter described as the UL TCI field.

In the second embodiment, the DCI including the specific field (e.g., the UL TCI field) may not include the SRI field. In other words, in the DCI format that schedules the PUSCH, the specific field may be included instead of the SRI field.

A UE where spatial relationship information (e.g., spatialRelationInfo-r17) specified in a particular release is configured for non-codebook PUSCH transmission and where an SRS resource set with usage = non-codebook is configured may expect the DCI for scheduling the PUSCH to include a UL TCI field.

The UE may interpret the UL TCI field as an existing SRI field. For example, the UE may determine that the codepoint of the UL TCI field is in accordance with (or is the same as) Table 7.3.1.1.2-28/29/30/31 described in TS 38.212 V16.2.0 of the existing Rel. 16 specification, and may determine one or more SRS resources included in the SRS resource set with usage=non-codebook for the spatial relationship information of the PUSCH based on the value of the UL TCI field. The UE may determine the UL TCI based on the one or more SRS resources.

This table 7.3.1.1.2-28/29/30/31 corresponds to the correspondence (table) between the SRI field and SRI for non-codebook-based PUSH transmission.

3 shows Table 7.3.1.1.2-29 described in TS 38.212 V16.2.0. This table relates to SRI indication for non-codebook based PUSCH transmission when L _max = 2. Note that the value of L _max may be set by the upper layer parameter "maxMIMO-Layers" indicating the maximum number of MIMO (Multi-Input Multi-Output) layers, or may be given by the maximum number of layers of PUSCH supported by the UE.

The Bit field mapped to index column indicates the value of the SRI field. N _SRS indicates the number of SRS resources configured for the SRS resource set. In FIG. 3, N _SRS = 2, 3, 4 are shown.

When making the above-mentioned interpretation, the UE may consider the Bit field mapped to index column in Figure 3 to indicate the value of the UL TCI field.

A UE with spatial relationship information (e.g., spatialRelationInfo-r17) specified in a particular release configured for non-codebook PUSCH transmission may expect the DCI for scheduling PUSCH to include the UL TCI field. In this case, the UE may not be configured with a purpose=non-codebook SRS resource set.

The UE may assume that the code point of the UL TCI field is mapped to one or more spatial related information configured/activated for the PUSCH. Each spatial related information may include an SRS as a reference reference signal. The UE may determine as at least one UL TCI of the configured/activated spatial related information based on the value of the UL TCI field. Each spatial related information may include an SRS as a reference reference signal.

4A and 4B, and 5A and 5B are diagrams showing examples of tables related to spatial relationship information indication according to the second embodiment. These tables relate to the correspondence between the UL TCI field (Codepoint) and the spatial relationship information (spatialRelationInfo(s)) for non-codebook-based PUSCH transmission. Figures 4A, 4B, 5A, and 5B correspond to the above-mentioned cases of L _max = 1, 2, 3, and 4, respectively.

Note that, similar to N _SRS in Fig. 3, every second column from the left in each figure may correspond to N _{SpatialRelationInfo} = 2, 3, 4. Here, N _{SpatialRelationInfo} may mean the number of spatial relationship information that is set/activated (for non-codebook-based transmission).

In Figures 4A, 4B, 5A and 5B, spatialRelationInfo(s) = i may mean the i-th spatial relationship information set for the PUSCH. spatialRelationInfo(s) = i may mean the i-th spatial relationship information set for the PUSCH from the smallest (or largest) spatial relationship information ID.

If the particular field is an SRS request field, the UL TCI may be determined based on (measurements of) the configured CSI-RS. In this case, the SRI field may be 0 bits. For example, the UE may determine the UL TCI (or precoder) based on measurements of the CSI-RS (associated CSI-RS) associated with the SRS (e.g., A-SRS) specified by the SRS request field.

According to the second embodiment described above, the UE can appropriately determine the UL TCI for the non-codebook-based PUSH.

Third Embodiment
The third embodiment relates to codebook-based/non-codebook-based PUSCH.

In a third embodiment, the spatial relationship of DMRS for PUSCH (PUSCH DMRS) may be set by the TCI state.

For example, when a TCI state is configured/activated for PUSCH (or PUSCH DMRS), the UL beam (spatial domain filter) for the codebook-based/non-codebook-based PUSCH may be determined by the same spatial domain filter used for reception of QCL type D (QCL-D) of that TCI state. For example, the UE may determine that the spatial domain filter for the PUSCH is the same spatial domain filter used for reception of the reference RS (e.g., SSB/CSI-RS) of QCL-D of the TCI state configured/activated for that PUSCH.

When multiple TCI states are configured/activated for a PUSCH (or PUSCH DMRS), one TCI state may be specified by a DCI (e.g., a specific field of the DCI (as described in the first and second embodiments)). The UL beam (spatial domain filter) for the codebook-based/non-codebook-based PUSCH may be determined by the same spatial domain filter used for receiving QCL type D (QCL-D) for the specified TCI state.

The DCI (or the above-mentioned specific fields of the DCI) that schedule the PUSH may be variable depending on the number of TCI states that are set/activated.

In addition, the TCI state (TCI state ID) in the third embodiment may mean the DL TCI state (DL TCI state ID). In this case, there is no need to newly set/activate the UL TCI state, and the DL TCI state can be used not only as the TCI state of the PDCCH/PDSCH/CSI-RS, but also as the UL TCI state of the PUSCH.

According to the third embodiment described above, the UE can appropriately determine the spatial domain filter for the PUSH based on the TCI state.

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

The specific UE capabilities may indicate at least one of the following:
Whether to support codebook-based PUSCH transmission with spatial relationship information for PUSCH including SSB/CSI-RS as reference signal (instead of SRS in codebook)
Whether to support non-codebook based PUSCH transmission with spatial relationship information for PUSCH including SSB/CSI-RS as reference signal (purpose=instead of non-codebook SRS)
The number (or maximum number) of spatial relationships for PUSCH transmissions that are supported.

In addition, at least one of the above-mentioned embodiments may be applied when the UE is configured with specific information related to the above-mentioned embodiments by higher layer signaling (if not configured, for example, the operation of Rel. 15/16 is applied). For example, the specific information may be information indicating that UL TCI is enabled (e.g., spatialRelation-r17), information indicating that U-TCI is enabled, information indicating that spatial relationship information for PUSCH including SSB/CSI-RS as a reference signal is enabled, information indicating the above-mentioned new transmission scheme, any RRC parameter for a specific release (e.g., Rel. 17), etc.

At least one of the above-mentioned embodiments may be applied in a case where the reference reference signals of the spatial relationship information (TCI state, UL TCI state) configured/activated in the UE are all DL-RS (e.g., SSB/CSI-RS) (in other words, spatial relationship information whose reference reference signal is SRS is not configured/activated).

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

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

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

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

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

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

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

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

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

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

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

The user terminal 20 may be a terminal compatible with at least one of the communication methods such as LTE, LTE-A, 5G, etc.

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 be called a waveform. In the wireless communication system 1, other radio access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL radio access methods.

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

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

User data, upper layer control information, System Information Block (SIB), etc. are transmitted by the PDSCH. User data, upper layer control information, etc. may be transmitted by the PUSCH. In addition, Master Information Block (MIB) may be transmitted by the PBCH.

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

In addition, the DCI for scheduling the PDSCH may be called a DL assignment, DL DCI, etc., and the DCI for scheduling the PUSCH may be called a UL grant, UL DCI, etc. In addition, the PDSCH may be replaced with DL data, and the PUSCH may be replaced with UL data.

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

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

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

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

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

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

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

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

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

The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, a control circuit, etc., which are described based on a common understanding in the technical field to which the present disclosure relates.

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

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

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

The transmitting/receiving antenna 130 may be constructed from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

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

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

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

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

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

The transceiver 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, and acquire user data, etc.

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

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

In addition, the transmitting unit and receiving unit of the base station 10 in the present disclosure may be constituted by at least one of the transmitting/receiving unit 120, the transmitting/receiving antenna 130, and the transmission path interface 140.

In addition, the transceiver unit 120 may transmit to the user terminal 20 Downlink Control Information (DCI) including a specific field used to determine the Uplink Transmission Configuration Indication state (UL TCI state).

The transceiver unit 120 may receive a codebook-based/non-codebook-based uplink shared channel (PUSCH) transmitted by the user terminal 20 applying a precoder determined based on the UL TCI state.

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

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

The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, a control circuit, etc., which are described based on a common understanding in the technical field to which the present disclosure relates.

The control unit 210 may control signal generation, mapping, etc. The control unit 210 may 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 configured from a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on a common understanding in the technical field related to the present disclosure.

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

The transmit/receive antenna 230 may be configured as an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

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

The transceiver 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 sequence to be transmitted, and output a baseband signal.

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

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

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

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

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

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

In addition, the control unit 210 may determine the uplink transmission configuration indication state (UL TCI state) based on a specific field included in the downlink control information (DCI).

The DCI may be a DCI format for scheduling the PUSCH (e.g., DCI format 0_0, 0_1, 0_2, etc.). The DCI may not include a Sounding Reference Signal (SRS) Resource Indicator (SRI) field.

The particular field may be a new field (e.g., may be called a UL beam field, a UL TCI field, etc.) that is not included in the existing Rel. 15 NR DCI format, or may be a field (e.g., an SRI field, an SRS request field, a precoding information field, etc.) that is included in the existing Rel. 15 NR DCI format.

The transceiver unit 220 may transmit a codebook-based uplink shared channel by applying a precoder determined based on the UL TCI state.

The precoder may be determined from a codebook for the number of antenna ports given by a higher layer parameter different from the higher layer parameter for the number of antenna ports for the sounding reference signal (SRS) resource, or the number of antenna ports indicated by a field of the DCI.

The control unit 210 may assume that when the DCI includes a field indicating the number of antenna ports, the precoding information and number of layers fields of the DCI have a fixed size regardless of the number of antenna ports indicated.

The transceiver unit 220 may transmit a non-codebook-based uplink shared channel by applying a precoder determined based on the UL TCI state.

The control unit 210 may determine that the code point of the specific field follows the same correspondence as the correspondence between the Sounding Reference Signal (SRS) Resource Indicator (SRI) field and the SRI for non-codebook-based uplink shared channel transmission, and may determine the UL TCI based on one or more SRS resources included in an SRS resource set of usage = non-codebook specified by the value of the specific field (e.g., the UL TCI for the one or more SRS resources may be used as the UL TCI).

The control unit 210 may determine that the code point of the particular field is mapped to one or more pieces of spatial relationship information configured or activated for the uplink shared channel, and may determine the UL TCI based on at least one piece of spatial relationship information specified by the value of the particular field (e.g., may determine that the spatial relationship information is the UL TCI).

(Hardware configuration)
The block diagrams used in the description of the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. The method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or may be realized using two or more devices that are physically or logically separated and directly or indirectly connected (for example, using wires, wirelessly, etc.). The functional blocks may be realized by combining the one device or the multiple devices with software.

Here, the functions include, but are not limited to, 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 the transmission function may be called a transmitting unit, transmitter, etc. In either case, as described above, there are no particular limitations on the method of realization.

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

In this disclosure, the terms apparatus, circuit, device, section, unit, etc. may be read interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the 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. Also, the processing may be performed by one processor, or the processing may be performed by two or more processors simultaneously, sequentially, or using other techniques. The processor 1001 may be implemented by one or more chips.

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

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

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

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

Storage 1003 is a computer-readable recording medium and may be constituted by at least one of, for example, a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (e.g., a compact disk (Compact Disc ROM (CD-ROM)), a digital versatile disk, a Blu-ray (registered trademark) disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, 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 (transmission and reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., to realize at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD). For example, the above-mentioned transmission and reception unit 120 (220), transmission and reception antenna 130 (230), etc. may be realized by the communication device 1004. The transmission and reception unit 120 (220) may be implemented as a transmission unit 120a (220a) and a reception unit 120b (220b) that are physically or logically separated.

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

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

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

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

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

Here, the numerology may be a communication parameter applied to at least one of the transmission and reception of a signal or channel. The numerology may indicate at least one of, for example, SubCarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame configuration, a specific filtering process performed by the transceiver in the frequency domain, and a specific windowing process performed by the transceiver 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, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.). A slot may also be a time unit based on numerology.

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

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

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

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

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

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

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

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

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

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

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

A resource block may also 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 partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by an index of the RB relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

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

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

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

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

The names used for parameters, etc. in this disclosure are not limiting in any respect. Furthermore, the formulas, etc. 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 the various names assigned to these various channels and information elements are not limiting in any respect.

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

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

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

Notification of information is not limited to the aspects/embodiments described in the present disclosure, and may be performed using other methods. For example, notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB), etc.), Medium Access Control (MAC) signaling), other signals, or combinations thereof.

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

In addition, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

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

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

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

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

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," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," and "panel" may be used interchangeably.

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

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

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

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

At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may be a device mounted on a moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may include a device that does not necessarily move during communication operation. 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.

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

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

In the present disclosure, operations that are described as being performed by a base station may in some cases also be performed by its upper node. In a network 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), a Serving-Gateway (S-GW), etc.), or a combination thereof.

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

Each aspect/embodiment described in this disclosure may be a part of any of the following: 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) (xG (x is, for example, an integer or a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The present invention may be applied to systems using 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), other appropriate wireless communication methods, next-generation systems that are based on these, etc. Also, a combination of multiple systems (for example, a combination of LTE or LTE-A and 5G) may be applied.

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

Any reference to an element using a designation such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish 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 precede the second element in some way.

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

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

In addition, "judgment" may be considered to be "judging" resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" may be considered to be "judging" some action.

In addition, "judgment (decision)" may be interpreted as "assuming," "expecting," "considering," etc.

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

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

In this disclosure, the term "A and B are different" may mean "A and B are different from each other." In addition, the term may 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 used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Additionally, the term "or," as used in this disclosure, is not intended to be an exclusive or.

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

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

Claims (6)

receiving a MAC Control Element (MAC CE) that activates one or more TCI states used for a Physical Downlink Shared Channel (PDSCH), a Physical Downlink Control Channel (PDCCH), a Channel State Information Reference Signal (CSI-RS), and a Physical Uplink Shared Channel (PUSCH) from a Transmission Configuration Indication state (TCI state) list;
A receiving unit that receives downlink control information (DCI);
a control unit for determining a TCI state from the one or more TCI states based on a specific field included in the DCI ;
A transmitting unit that transmits a non-codebook based uplink shared channel by applying a spatial domain filter that is determined based on the TCI state. The terminal of claim 1 , wherein the DCI does not include a Sounding Reference Signal Resource Indicator (SRI) field. The terminal of claim 1, wherein the TCI state includes information regarding a Synchronization Signal Block (SSB) or a CSI-RS. receiving a MAC Control Element (MAC CE) activating one or more TCI states for a Physical Downlink Shared Channel (PDSCH), a Physical Downlink Control Channel (PDCCH), a Channel State Information Reference Signal (CSI-RS), and a Physical Uplink Shared Channel (PUSCH) from a list of Transmission Configuration Indication states (TCI states);
receiving Downlink Control Information (DCI);
determining a TCI state from the one or more TCI states based on a particular field included in the DCI ;
and applying a spatial domain filter determined based on the TCI state to transmit a non-codebook based uplink shared channel. transmit a MAC Control Element (MAC CE) for activating one or more TCI states used for a Physical Downlink Shared Channel (PDSCH), a Physical Downlink Control Channel (PDCCH), a Channel State Information Reference Signal (CSI-RS), and a Physical Uplink Shared Channel (PUSCH) from a Transmission Configuration Indication state (TCI state) list;
A transmitter that transmits Downlink Control Information (DCI);
a control unit for indicating a TCI state from the one or more TCI states based on a specific field included in the DCI;
a receiving unit for receiving a codebook-based uplink shared channel transmitted by applying a spatial domain filter determined based on the TCI state. A system including a terminal and a base station,
The terminal includes:
receiving a MAC Control Element (MAC CE) that activates one or more TCI states used for a Physical Downlink Shared Channel (PDSCH), a Physical Downlink Control Channel (PDCCH), a Channel State Information Reference Signal (CSI-RS), and a Physical Uplink Shared Channel (PUSCH) from a Transmission Configuration Indication state (TCI state) list;
A receiving unit that receives downlink control information (DCI);
a control unit for determining a TCI state from the one or more TCI states based on a specific field included in the DCI;
a transmitter for transmitting a non-codebook based uplink shared channel by applying a spatial domain filter determined based on the TCI state;
having
The base station transmits the DCI.

Images