Terminal, wireless communication method, base station and system

Abstract

To appropriately control PUSCH transmission.SOLUTION: A terminal according to one aspect of the present disclosure includes: a receiving unit that receives higher layer signaling that sets transmission configuration indication (TCI) states and a single downlink control information (DCI) that schedules a plurality of uplink shared channels (PUSCHs); and a control unit that, when information regarding the number of antenna ports for the plurality of PUSCHs is notified by the single DCI, applies each of the set multiple TCI states to a plurality sets of the antenna ports that are based on the information regarding the number of antenna ports.SELECTED DRAWING: Figure 4

Description

[Technical Field]

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

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

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

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

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

[0006] However, there is still a lack of research on how to control the UL beam used by UEs when the UL TCI state is introduced. Unless this control is clarified, there is a risk that the increase in communication throughput will be limited.

[0007] Therefore, one 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. [Means for solving the problem]

[0008] A terminal according to one embodiment of the present disclosure includes: a receiving unit that receives higher layer signaling that sets a transmission configuration indication (TCI) state and a single downlink control information (DCI) that schedules multiple uplink shared channels (PUSCHs); and a control unit that, when information regarding the number of antenna ports for the multiple PUSCHs is notified by the single DCI, applies each of the set multiple TCI states to multiple sets of antenna ports based on the information regarding the number of antenna ports. [Effects of the Invention]

[0009] According to one aspect of the present disclosure, PUSCH transmission can be appropriately controlled. [Brief explanation of the drawings]

[0010] [Figure 1] 1A and 1B are diagrams illustrating an example of RRC parameters related to the number of PUSCH ports. [Figure 2]2A and 2B are diagrams illustrating an example of MAC CE with respect to the number of PUSCH ports. [Figure 3] 3A to 3C are diagrams illustrating another example of MAC CE regarding the number of PUSCH ports in the second embodiment. [Figure 4] 4A and 4B are diagrams showing an example of the correspondence relationship between the PUSCH port number field and the number of PUSCH ports in the second embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] (TCI, spatial relations, QCL) In NR, it is considered that a 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 a signal / channel; in the present disclosure, "A / B" may similarly be read as "at least one of A and B") based on a transmission configuration indication state (TCI state).

[0012] The TCI state may represent that which is applied to a downlink signal / channel, and the equivalent of the TCI state which is applied to an uplink signal / channel may be expressed as a spatial relation.

[0013] 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 for each channel or signal.

[0014] A 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 parameter (e.g., spatial Rx parameter) is the same between these different signals / channels (i.e., they are QCLs with respect to at least one of these).

[0015] The spatial reception parameters may correspond to a reception beam (e.g., a reception analog beam) of the UE, and the beam may be determined based on a spatial QCL. A QCL (or at least one element of a QCL) in the present disclosure may be replaced with an sQCL (spatial QCL).

[0016] A plurality of types (QCL types) of QCLs may be defined. For example, four QCL types A and B may be provided, each having different parameters (or parameter sets) that can be assumed to be the same. The parameters (which may also be referred to as QCL parameters) are listed below: 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 receiving parameters.

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

[0018] The assumption by a UE that a given Control Resource Set (CORESET), channel, or reference signal is in a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be referred to as a QCL assumption.

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

[0020] The TCI state may be, for example, information about the QCL between a target channel (or a Reference Signal (RS) for the 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 thereof.

[0021] In the present disclosure, higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and the like, or a combination thereof.

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

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

[0024] The channel / signal to which the TCI state is applied may be called a target channel / reference signal (target channel / RS), or simply a target, and the other signal may be called a reference reference signal (reference RS), source RS, or simply a reference.

[0025] The channel for which the TCI state is set (designated) may be, for example, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), or the like.

[0026] Furthermore, 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.

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

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

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

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

[0031] An SRS resource set may be associated with (or group together) a predetermined number of SRS resources, each of which may be identified by an SRS Resource Indicator (SRI) or SRS Resource Identifier (ID).

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

[0033] Here, the SRS resource type may indicate any one of periodic SRS (P-SRS), semi-persistent SRS (SP-SRS), and 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.

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

[0035] 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 the case of codebook-based transmission. The UE may determine a precoder for PUSCH transmission based on the SRI in the case of non-codebook-based transmission.

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

[0037] 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).

[0038] 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 predetermined reference signal.

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

[0040] The spatial relationship information of the SRS may include a serving cell index, a BWP index (BWP ID), etc. corresponding to the predetermined reference signal.

[0041] When the UE is configured with spatial relationship information regarding the SSB or CSI-RS and the SRS 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 for receiving the SSB or CSI-RS (spatial domain receive filter). 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.

[0042] 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. That is, 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.

[0043] 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). 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., the SRI) for PUSCH transmission.

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

[0045] The UE may determine the TPMI and the 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, the number of layers, etc. from an uplink codebook for the same number of SRS ports as the number of SRS ports indicated by the upper layer parameter "nrofSRS-Ports" configured for the SRS resource specified by the SRI field.

[0046] In Rel. 15 / 16 NR, when non-codebook-based transmission is used for PUSCH, the UE may be 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 (a 2-bit SRI field).

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

[0048] If a CSI-RS (which may be referred to as an associated CSI-RS) associated with the SRS resource (or an SRS resource set to which the SRS resource belongs) is configured by a higher layer, the transmit beam for the PUSCH may be calculated based on (measurements of) the configured associated CSI-RS. Otherwise, the transmit beam for the PUSCH may be specified by the SRI.

[0049] 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 "non-codebook."

[0050] In this disclosure, codebook-based PUSCH (codebook-based PUSCH transmission, codebook-based transmission) may refer to a PUSCH when a 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 a PUSCH when a UE is configured with "non-codebook" as the transmission scheme.

[0051] (UL TCI condition) 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 interchangeably read as the TCI state for PDCCH / PDSCH.

[0052] The UL TCI state may be configured in the UE by spatial relation information specified in a specific 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 a unified TCI state (U-TCI state), a spatial relation, a spatial relation of a specific release, etc.

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

[0054] The channel / signal (which may be referred to as a target channel / RS) to 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 Physical Random Access Channel (PRACH), an SRS, etc.

[0055] Furthermore, 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.).

[0056] 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 configured (or specified) or implicitly determined by higher layer signaling (e.g., RRC signaling, MAC CE, etc.).

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

[0058] The QCL type indicated by the UL TCI state may be the existing QCL type AD or may be another QCL type, and may include a predetermined spatial relationship, associated antenna ports (port index), etc.

[0059] When a UE is assigned an associated panel ID for an UL transmission (e.g., specified by DCI), the UE may perform the UL transmission using the 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.

[0060] However, there is still a lack of research on how to control the UL beam used by UEs when the UL TCI state is introduced. Unless this control is clarified, there is a risk that the increase in communication throughput will be limited.

[0061] 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 that the SRS of usage = codebook is not set. In this case, it is possible that the base station determines the TPMI, transmission rank, etc. based on (feedback report of) DL CSI measurement by the UE, rather than SRS measurement.

[0062] 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 the number of antenna ports for PUSCH when the SRI field is not used.

[0063] Therefore, the present inventors have conceived a method for appropriately transmitting PUSCH, taking into consideration the case where the UL TCI state is introduced.

[0064] 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 independently or in combination. Note that the embodiments of the present disclosure may be used when the UL TCI state is not introduced.

[0065] In the present disclosure, "A / B" may also mean "at least one of A and B."

[0066] In the present disclosure, the terms activate, deactivate, indicate, select, configure, update, determine, etc. may be read interchangeably.

[0067] In the present disclosure, terms such as panel, beam, panel group, beam group, Uplink (UL) transmitting entity, TRP, spatial relationship information (SRI), spatial relationship, 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, QCL, etc. may be interpreted as interchangeable.

[0068] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interchangeable. "Spatial relationship information" may be interchangeable with "set of spatial relationship information," "one or more pieces of spatial relationship information," etc. The TCI state and TCI may be interchangeable with each other.

[0069] In this disclosure, the terms index, ID, indicator, and resource ID may be interchangeable. Also, in this disclosure, the terms sequence, list, set, group, cluster, and subset may be interchangeable.

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

[0071] In the following embodiments, the spatial relationship information ID (spatialRelationInfoId), the spatial relationship information ID defined in a specific release (for example, spatialRelationInfoId-r17 defined in Rel.17), the TCI state ID defined in a specific release (for example, TCIstateId-r17 defined in Rel.17), etc. may be interchangeable. Note that the names of these parameters are not limited to these.

[0072] In the following description of the embodiments, terms such as "Spatial Relation Information (SRI)," "Spatial Relation Information for PUSCH," "Spatial Relation," "UL Beam," "UE Transmit Beam," "UL TCI," "UL TCI State," "Spatial Relation of UL TCI State," SRS Resource Indicator (SRI), SRS Resource, Precoder, etc. may be interchangeable.

[0073] Note that the following embodiments assume a case where a UE transmits a PUSCH based on the UL TCI state, but may be applied to other cases. Also, the number of antenna ports for PUSCH transmission (hereinafter simply referred to as PUSCH ports) in the following embodiments does not depend on (is independently configured / activated / specified) the number of antenna ports for SRS resources (given by, for example, a higher layer parameter "nrofSRS-Ports").

[0074] (Wireless communication method) First Embodiment In the first embodiment, the UE is notified of the number of PUSCH ports by RRC configuration.

[0075] The number of PUSCH ports may be configured in the UE by higher layer signaling (for example, an RRC information element "PUSCH-Config" for PUSCH configuration).

[0076] 1A and 1B are diagrams illustrating an example of RRC parameters related to the number of PUSCH ports in 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 the present disclosure, names of RRC information elements, RRC parameters, etc. may be given a suffix (e.g., "_r16", "_r17", etc.) indicating that they are introduced in specific resources.

[0077] 1A, the PUSCH configuration ("PUSCH-Config") includes a parameter "nrofPort" that indicates one or more candidate values ​​for the number of PUSCH ports (up to maxNrOfCandidateValue). The candidate values ​​are 1, 2, and 4, but other values ​​(e.g., 8) may also be used.

[0078] A UE configured with the parameter including only one candidate value may apply the configured candidate value as the number of PUSCH ports.

[0079] A UE to which the parameter including multiple candidate values ​​is set may determine that the number of PUSCH ports is set depending on the TCI state corresponding to the PUSCH, may determine that the number of PUSCH ports is related to the TCI state, or may assume that the number of PUSCH ports is notified by the MAC CE / DCI.

[0080] As shown in FIG. 1B, the PUSCH configuration ("PUSCH-Config") may include a parameter "nrofPort" indicating one candidate value for the number of PUSCH ports. In this case, the UE may apply the value set by the parameter "nrofPort" as the number of PUSCH ports unless the number of PUSCH ports is additionally configured / activated / instructed by the TCI state, MAC CE / DCI, etc. Otherwise, the UE may apply the number of PUSCH ports additionally configured / activated / instructed by the TCI state, MAC CE / DCI, etc. to PUSCH transmission.

[0081] For example, when a UE is scheduled to transmit a PUSCH in a TCI state corresponding to an RRC information element ("TCI-State") related to a TCI state in which a parameter for the number of PUSCH ports is set, the UE may determine that the number of ports for the PUSCH is specified by the number of PUSCH ports included in "TCI-State" rather than by "nrofPort" in "PUSCH-Config".

[0082] Considering the case where the antenna configuration differs for each UE panel, it is preferable to set the number of PUSCH ports for each UE panel. Therefore, a parameter indicating candidate values ​​for the number of PUSCH ports may be set for each UE panel (for example, in association with a UE panel ID).

[0083] Note that the parameter indicating the candidate value for the number of PUSCH ports may be set for each TRP (for example, in association with a TRP ID).

[0084] The first embodiment may be applied only to UEs that have reported or support a particular UE capability.

[0085] The specific UE capabilities may indicate at least one of the following: The number of supported PUSCH port candidate values ​​(e.g., whether one candidate value is supported or multiple candidate values ​​are supported), Support different numbers of PUSCH ports for different UE panels? · Supports different numbers of PUSCH ports for different TRPs?

[0086] Furthermore, the first embodiment may be applied when specific information is configured in the UE by higher layer signaling (when not configured, for example, the operation of Rel. 15 / 16 is applied). For example, the specific information may be a parameter "nrofPort" indicating one or more candidate values ​​for the number of PUSCH ports, or may be any RRC parameter for a specific release (for example, Rel. 17).

[0087] A configuration in which the PUSCH configuration ("PUSCH-Config") includes a parameter "nrofPort" indicating one candidate value for the number of PUSCH ports is preferable because it can suppress an increase in communication overhead when only one candidate value for the number of PUSCH ports is required (for example, when mode 2 ('fullpoweMode2') is not set as the UL full power transmission mode (RRC parameter "ul-FullPowerTransmission-r16")).

[0088] In addition, when mode 2 ('fullpoweMode2') is configured as the UL full power transmission mode (RRC parameter 'ul-FullPowerTransmission-r16'), the UE may expect that multiple candidate values ​​for the number of PUSCH ports will be configured by RRC.

[0089] According to the first embodiment described above, the number of PUSCH ports can be appropriately determined.

[0090] <Second embodiment> In the second embodiment, the UE is notified of the number of PUSCH ports by the MAC CE.

[0091] The number of PUSCH ports may be signaled by a dedicated MAC CE that signals the number of PUSCH ports, or may be signaled by the MAC CE that activates the TCI state for the PUSCH.

[0092] The number of PUSCH ports notified by the MAC CE may be the same for all TCI states, or may be an independent value for each activated TCI state.

[0093] 2A and 2B are diagrams illustrating an example of a MAC CE related to the number of PUSCH ports in the second embodiment. The MAC CE in these examples may be a MAC CE for activating X TCI states for the PUSCH from the TCI states configured by RRC. The activated TCI states may be mapped to code points of the DCI field indicating the TCI states for the PUSCH.

[0094] In the example of FIG. 2A, the MAC CE includes an R field, a serving cell ID field, a BWP ID field, and a TCI state ID field. i The PUSCH port count field includes a field indicating the number of PUSCH ports, and a PUSCH port count field (nrofPort field) indicating the number of PUSCH ports.

[0095] The serving cell ID field and the BWP ID field indicate the serving cell and the BWP to which the MAC CE applies. The R field indicates a reserved field to be used in the future.

[0096] TCI State ID iThe field indicates the TCI state to be activated and may be mapped to codepoint (i) of the DCI field indicating the TCI state for the PUSCH. In this example, the maximum number of UL TCI states is 64 and the TCI State ID field is 6 bits, but the size of the TCI State ID field may be other numbers.

[0097] In this example, the number of PUSCH ports field is represented by 2 bits, but may be of another bit size, for example, may be represented by 1 bit.

[0098] A UE that receives the MAC CE of FIG. 2A may determine that the number of PUSCH ports indicated by one PUSCH port number field applies to the X+1 activated TCI state IDs.

[0099] The example in Figure 2B shows the TCI state ID i Number of PUSCH ports corresponding to the field i Field(nrofPort i This differs from Figure 2A in that it includes a field.

[0100] The UE that receives the MAC CE in Figure 2B will receive the TCI state ID to be activated. i Regarding the number of PUSCH ports, i In this case, the UE may be implicitly instructed about the number of PUSCH ports by the TCI state indicated by the TCI field of the DCI.

[0101] It should be noted that the MAC CE for activating the TCI state of the present disclosure is not limited to those shown in Figures 2A and 2B. For example, i Instead of a field, a 1-bit T i The number of fields may be the same as the number of TCI state IDs configured by RRC. iThe field may, when set to 1, indicate that the TCI state with TCI state ID i is activated and is mapped to the codepoint of the TCI field of the DCI.

[0102] In addition, the MAC CE for activating the TCI state may include a CORESET pool index field indicating a CORESET pool index, which may mean that the codepoint of the TCI field included in the DCI indicating the TCI state activated by the MAC CE applies to the configured CORESET with the CORESET pool index indicated by this field.

[0103] In the case where a single DCI-based MTRP is used, the MAC CE may activate multiple TCI state combinations per DCI codepoint. In this case, the TCI state IDs in Figures 2A and 2B i Instead of a field, the TCI state ID i,j It may contain fields.

[0104] TCI State ID i,j The field may indicate the j-th activated TCI state that is mapped to codepoint (i) of the DCI field indicating the TCI state for the PUSCH, where j may correspond to the TRP.

[0105] 3A to 3C are diagrams illustrating another example of MAC CE regarding the number of PUSCH ports in the second embodiment.

[0106] In these examples, DCI codepoint i represents two TCI states (TCI state ID i,1 and TCI status ID i,2 The number of TCI states mapped to a code point does not necessarily have to be two, but may be any number such as 1, 2, 3, or 4.

[0107] The MAC CE in Figure 3A uses the TCI state IDk,j (k is any integer) Number of PUSCH ports corresponding to the field j Field(nrofPort j For example, the nrofPort1 field may indicate the number of PUSCH ports for TRP1, and the TCI state ID 0,1 Field, TCI State ID 1,1 Fields, ..., TCI State ID X,1 may apply to the TCI state indicated by each field.

[0108] The MAC CE in Figure 3B uses the TCI state ID i,k (k is any integer) Number of PUSCH ports corresponding to the field i Field(nrofPort i For example, the nrofPort0 field contains the set of TCI states (TCI state IDs) corresponding to codepoint 0. 0,1 Field, TCI State ID 0,2 The TCI state set may also indicate the number of PUSCH ports that apply to the TCI state set (each indicated by a field).

[0109] The MAC CE in Figure 3C uses the TCI state ID i,j Number of PUSCH ports corresponding to the field i,j Field(nrofPort i,j field), e.g., the TCI state ID to be activated i,j For the TCI state, the number of PUSCH ports i,j It may be determined that the number of PUSCH ports indicated by the field is applied.

[0110] The correspondence between the number of PUSCH ports field (nrofPort field) shown in Figures 2A, 2B, 3A-3C, etc. and the number of PUSCH ports may be defined in advance by specifications, may be set by higher layer signaling (for example, may be set by the candidate values ​​shown in the first embodiment), or may be determined based on UE capabilities.

[0111] 4A and 4B are diagrams showing an example of the correspondence relationship between the PUSCH port number field and the number of PUSCH ports in the second embodiment. In Fig. 4A, for example, values ​​0, 1, 2, and 3 in the PUSCH port number field are associated with a single port (1 port), 2 ports (2 ports), 4 ports (4 ports), and 8 ports (8 ports), respectively.

[0112] In FIG. 4B, the UE is configured by RRC with 2 and 4 as candidate values ​​for the number of PUSCH ports, which are mapped to values ​​of 0 and 1 in the number of PUSCH ports field, respectively.

[0113] The second embodiment may be applied only to UEs that have reported or support a particular UE capability.

[0114] The specific UE capabilities may indicate at least one of the following: - Supports specifying the number of PUSCH ports using MAC CE Supports specifying different numbers of PUSCH ports for different TCI states · In the case where a single DCI-based MTRP is used, is it possible to support different numbers of PUSCH ports for different TRPs?

[0115] Furthermore, the second embodiment may be applied when specific information is configured in the UE by higher layer signaling (when not configured, for example, the operation of Rel. 15 / 16 is applied). For example, the specific information may be a parameter "nrofPort" indicating one or more candidate values ​​for the number of PUSCH ports, or may be any RRC parameter for a specific release (for example, Rel. 17).

[0116] According to the second embodiment described above, the number of PUSCH ports can be appropriately determined.

[0117] <Third embodiment> In the third embodiment, the UE is notified of the number of PUSCH ports by DCI.

[0118] The number of PUSCH ports may be signaled by a new field of the DCI (e.g., a number of PUSCH ports field (nrofPort field)). The correspondence relationship between the number of PUSCH ports field and the number of PUSCH ports may be defined in advance by a specification, may be set / activated by higher layer signaling (e.g., may be set by the candidate value shown in the first embodiment, or may be activated by the MAC CE shown in the second embodiment), or may be determined based on UE capabilities. Examples of the correspondence relationship may be similar to those shown in FIGS. 4A and 4B.

[0119] In the case where single DCI based MTRP is used, if multiple TCI states are specified for PUSCH transmission, one of the following may be used: One PUSCH port number is notified by DCI, and the PUSCH port number is applied to the multiple TCI states (multiple TRPs). A plurality of numbers of PUSCH ports are notified by DCI, and a different number of PUSCH ports from the plurality of numbers of PUSCH ports is applied to each of the plurality of TCI states (plurality of TRPs).

[0120] The third embodiment may be applied only to UEs that have reported or support a particular UE capability.

[0121] The specific UE capabilities may indicate at least one of the following: -Does it support specifying the number of PUSCH ports using DCI? · In the case where a single DCI-based MTRP is used, is it possible to support different numbers of PUSCH ports for different TCI states / different TRPs?

[0122] Furthermore, the third embodiment may be applied when specific information is configured in the UE by higher layer signaling (when not configured, for example, the operation of Rel. 15 / 16 is applied). For example, the specific information may be a parameter "nrofPort" indicating one or more candidate values ​​for the number of PUSCH ports, or may be any RRC parameter for a specific release (for example, Rel. 17).

[0123] According to the third embodiment described above, the number of PUSCH ports can be appropriately determined.

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

[0125] 5 is a diagram illustrating 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).

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

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

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

[0129] 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 located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The locations and numbers of the cells and user terminals 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.

[0130] 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0152] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0166] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0167] The transceiver 120 may transmit information regarding the number of Physical Uplink Shared Channel (PUSCH) ports to the user terminal 20, independently of the number of antenna ports for sounding reference signal (SRS) resources.

[0168] The control unit 110 may receive a PUSCH transmitted using the number of PUSCH ports determined by the user terminal 20 based on the information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0186] Note that the control unit 210 may determine the number of PUSCH ports based on information regarding the number of Physical Uplink Shared Channel (PUSCH) ports that is notified independently of the number of antenna ports for sounding reference signal (SRS) resources.

[0187] The transmitting / receiving unit 220 may transmit the PUSCH using the determined number of PUSCH ports.

[0188] The control unit 210 may determine the number of PUSCH ports based on a Radio Resource Control (RRC) parameter indicating one or more candidate values ​​for the number of PUSCH ports.

[0189] The control unit 210 may determine the number of PUSCH ports based on a Medium Access Control (MAC) control element that includes a field for the number of PUSCH ports.

[0190] The control unit 210 may determine the number of PUSCH ports based on Downlink Control Information (DCI) that includes a field for the number of PUSCH ports.

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

[0192] 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 transmission may be called a transmitting unit, transmitter, etc. As mentioned above, the implementation method of each is not particularly limited.

[0193] For example, a base station, a user terminal, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 8 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. The above-described 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.

[0194] In this disclosure, terms such as 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 drawings, or may be configured to exclude some of the devices.

[0195] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

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

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

[0198] The processor 1001 also reads 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 in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be realized in a similar manner.

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

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

[0201] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. 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 / reception unit 120 (220), transmission / reception antenna 130 (230), etc. may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be implemented as a transmission unit 120a (220a) and a reception unit 120b (220b) that are physically or logically separated.

[0202] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

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

[0204] 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 such hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

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

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

[0207] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), the number of symbols per TTI, a radio frame structure, a specific filtering process performed by a transceiver in the frequency domain, and a specific windowing process performed by a transceiver in the time domain.

[0208] A slot may be composed of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol), and may be a time unit based on numerology.

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

[0210] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to 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 the present disclosure may be interchangeable.

[0211] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 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.

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

[0213] The TTI may be a transmission time unit for a channel-encoded 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) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0214] 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 for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

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

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

[0217] A resource block (RB) is a resource allocation unit in the time domain and the 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, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

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

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

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

[0221] A Bandwidth Part (BWP), which may also be referred to as a fractional 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 their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

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

[0223] 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 replaced with "BWP."

[0224] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. 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, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0225] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by a predetermined index.

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

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

[0228] Furthermore, 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.

[0229] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0230] 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) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0231] Note that 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. Furthermore, the RRC signaling may be called an RRC message, such as an RRC connection setup message or an RRC connection reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

[0232] Furthermore, 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).

[0233] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

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

[0235] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if 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), then these wired and / or wireless technologies are included within the definition of transmission media.

[0236] 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., base stations).

[0237] In the present disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial 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," "panel," etc. may be used interchangeably.

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

[0239] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

[0240] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

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

[0242] 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 mobile object, or the mobile object itself. The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (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 also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

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

[0244] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0245] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal 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) and a Serving-Gateway (S-GW)), or a combination thereof.

[0246] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the specific order presented.

[0247] Each aspect / embodiment described in the present disclosure may be related to 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 that use 802.20, Ultra-Wide Band (UWB), Bluetooth (registered trademark), or other appropriate wireless communication methods, or to next-generation systems that are based on and extend these systems. Furthermore, the present invention may be applied to a combination of multiple systems (for example, a combination of LTE or LTE-A and 5G).

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

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

[0250] 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, etc.

[0251] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.

[0252] Also, "decision" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. In other words, "decision" may be considered to be "deciding" on some action.

[0253] Furthermore, "judgment (decision)" may be interpreted as "assuming," "expecting," "considering," or the like.

[0254] As used in this disclosure, the terms "connected," "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 elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0255] 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, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.

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

[0257] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

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

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

Claims

1. a receiver for receiving higher layer signaling for setting a transmission configuration indication (TCI) state and a single downlink control information (DCI) for scheduling multiple uplink shared channels (PUSCHs); A terminal having a control unit that, when information regarding the number of antenna ports for the multiple PUSHs is notified by the single DCI, applies each of the multiple TCI states that have been set to multiple sets of antenna ports based on the information regarding the number of antenna ports.

2. The terminal according to claim 1, wherein the TCI state is a unified TCI state.

3. receiving higher layer signaling for setting a transmission configuration indication (TCI) state and a single downlink control information (DCI) for scheduling multiple uplink shared channels (PUSCHs); When information regarding the number of antenna ports for the plurality of PUSHs is notified by the single DCI, applying each of the plurality of set TCI states to a plurality of sets of antenna ports based on the information regarding the number of antenna ports.

4. a transmitter for transmitting higher layer signaling for setting a transmission configuration indication (TCI) state and a single downlink control information (DCI) for scheduling multiple uplink shared channels (PUSCHs); A base station having a control unit that, when information regarding the number of antenna ports for the multiple PUSHs is notified by the single DCI, applies each of the multiple TCI states that have been set to multiple sets of antenna ports based on the information regarding the number of antenna ports.

5. A system including a terminal and a base station, The terminal a receiver for receiving higher layer signaling for setting a transmission configuration indication (TCI) state and a single downlink control information (DCI) for scheduling multiple uplink shared channels (PUSCHs); a control unit that applies each of the plurality of TCI states to a plurality of sets of antenna ports based on the information on the number of antenna ports when information on the number of antenna ports for the plurality of PUSCHs is notified by the single DCI, The base station A system comprising a transmitter that transmits the higher layer signaling and the single DCI.

Images