Terminals, wireless communication methods, base stations and systems

JP7876521B2Active Publication Date: 2026-06-19NTT DOCOMO INC
View PDF 7 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
NTT DOCOMO INC
Filing Date
2021-05-31
Publication Date
2026-06-19

AI Technical Summary

Technical Problem

Existing wireless communication systems, such as Rel.15/16 NR, control power and modulation and coding scheme (MCS) equally across antenna ports, which hinders the achievement of faster communication in future Multi Input Multi Output (MIMO) environments like 6G.

Method used

Implementing power and MCS control for each layer or port in MIMO systems, allowing for optimal power allocation and differential MCS application across layers using methods based on DCI and RRC parameters.

Benefits of technology

Enables increased communication throughput by optimizing power and MCS distribution for each layer, addressing the limitations of equal power/MCS control in existing systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007876521000001
    Figure 0007876521000001
  • Figure 0007876521000002
    Figure 0007876521000002
  • Figure 0007876521000003
    Figure 0007876521000003
Patent Text Reader

Abstract

A terminal according to one aspect of the present disclosure comprises: a control unit that performs control to apply different power ratios to a plurality of layers; and a transmission unit that applies the different power ratios to transmit physical uplink shared channels of the plurality of layers. This aspect of the present disclosure makes it possible to appropriately perform power / MCS control for each layer / port.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] This disclosure relates to terminals and wireless communication methods in next-generation mobile communication systems. 、 base station and system Regarding. [Background technology]

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

[0003] Successor systems to LTE (for example, 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.) 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 [Overview of the project]

Problems to be Solved by the Invention

[0005] In Rel.15 / 16 NR, for the transmission and reception of channels / signals using multiple antenna ports, control is performed such that the power is equal between antenna ports, and equal power / the same modulation and coding scheme (MCS) is applied between layers.

[0006] However, in future wireless communication systems (such as 6G), it is required to achieve faster communication in a Multi Input Multi Output (MIMO) environment. However, there has been no further study on how to achieve faster communication. If this is not clarified, there is a risk that the increase in communication throughput will be suppressed.

[0007] Therefore, one object of the present disclosure is to provide a terminal and a wireless communication method that can appropriately perform power / MCS control for each layer / port. 、 Base station and system as one of the purposes.

Means for Solving the Problems

[0008] A terminal according to one aspect of the present disclosure A receiver that receives parameters for determining the first transmit power value corresponding to the first panel for Multi Input Multi Output (MIMO), and a second transmit unit corresponding to the second panel for MIMO. Power The value is determined based on the first transmission power value. su The system control unit, and the First transmission Power Value is applied to perform Panel 1 the transmission of the uplink shared channel of Next, the second transmit power value is applied to transmit on the uplink sharing channel of the second panel. a transmission unit.

Effects of the Invention

[0009] According to one aspect of the present disclosure, power / MCS control for each layer / port can be appropriately performed.

Brief Description of the Drawings

[0010] [Figure 1]Figures 1A and 1B show an example of a TPMI notification to a UE performing transmission for two antenna ports, where transform precoding is disabled and the maximum rank is set to 2. [Figure 2] Figure 2 shows an example of the correspondence between the TPMI index and the precoding matrix W. [Figure 3] Figure 3 shows a conceptual diagram of the first embodiment. [Figure 4] Figures 4A and 4B show an example of a TPMI notification to a UE performing transmission for two antenna ports in Embodiment 1.1.1, where transform precoding is disabled and maximum rank = 2. [Figure 5] Figure 5 shows an example of the correspondence between the TPMI index and the precoding matrix W in Embodiment 1.1.2. [Figure 6] Figures 6A and 6B show an example of the correspondence between a certain index and the power distribution matrix R in Embodiment 1.1.3. [Figure 7] Figure 7 shows an example of RRC information elements / parameters for setting the power ratio according to Embodiment 1.2. [Figure 8] Figure 8 shows an example of applying the power ratio to non-codebook-based transmission in the first embodiment. [Figure 9] Figure 9 shows a conceptual diagram of the second embodiment. [Figure 10] Figures 10A and 10B show an example of determining the MCS for each layer based on the MCS field in Embodiment 2.1. [Figure 11] Figures 11A and 11B show an example of determining the MCS for multiple layers according to Embodiment 2.1. [Figure 12] Figure 12 shows an example of an MCS table where a single value in the MCS index corresponds to the MCS of multiple layers. [Figure 13] Figure 13 shows an example of RRC information elements / parameters for setting up the MCS for each layer according to Embodiment 2.2. [Figure 14] Figure 14 shows an example of determining the layer-by-layer power ratio and MCS based on a specific field in a modified version of the first and second embodiments. [Figure 15] Figure 15 shows an example of per-push power control for an MTRP pusher based on a further modification of the first embodiment. [Figure 16] Figure 16 shows an example of per-push MCS control for an MTRP pusher based on a further modification of the second embodiment. [Figure 17] Figure 17 shows a conceptual diagram of the third embodiment. [Figure 18] Figures 18A and 18B show an example of a CSI report including layer-specific CQIs in the fourth embodiment. [Figure 19] Figures 19A and 19B show an example of determining the MCS for multiple layers according to Embodiment 2.1. [Figure 20] Figure 20 shows an example of per-PDSCH MCS control for MTRP PDSCH based on a further modification of the third embodiment. [Figure 21] Figure 21 shows an example of a schematic configuration of a wireless communication system according to one embodiment. [Figure 22] Figure 22 shows an example of the configuration of a base station according to one embodiment. [Figure 23] Figure 23 shows an example of the configuration of a user terminal according to one embodiment. [Figure 24] Figure 24 shows an example of the hardware configuration of a base station and a user terminal according to one embodiment. [Modes for carrying out the invention]

[0011] (PUSCH precoder) In NR, user terminals (User Equipment (UE)) may support at least one of codebook-based transmission and non-codebook-based transmission.

[0012] For example, the UE may use at least a Sounding Reference Signal (SRS) Resource Index (SRI) to determine a precoder (precoding matrix) for at least one of CB-based and NCB-based Physical Uplink Shared Channel (PUSCH) transmissions.

[0013] The UE may receive information used to transmit a measurement reference signal (e.g., a Sounding Reference Signal (SRS)) (e.g., SRS configuration information, such as parameters in the "SRS-Config" of the RRC control element).

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

[0015] A single SRS resource set may be associated with a predetermined number of SRS resources (a predetermined number of SRS resources may be grouped together). Each SRS resource may be identified by an SRS Resource Indicator (SRI) or an SRS Resource Identifier.

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

[0017] Furthermore, the application (RRC parameter "usage", L1 (Layer-1) parameter "SRS-SetUse") may be, for example, beam management, codebook (CB), noncodebook (NCB), antenna switching, etc. SRS for codebook or noncodebook applications may be used to determine the precoder for SRI-based codebook-based or noncodebook-based uplink shared channel (PUSCH) transmission.

[0018] For CB-based transmissions, the UE may determine the precoder for push transmissions based on the SRI, Transmitted Rank Indicator (TRI), and Transmitted Precoding Matrix Indicator (TPMI), etc. For NCB-based transmissions, the UE may determine the precoder for push transmissions based on the SRI.

[0019] SRI, TRI, TPMI, etc., may be notified to the UE using Downlink Control Information (DCI). SRI may be specified by the SRS Resource Indicator field (SRI field) of DCI, or by the parameter "srs-ResourceIndicator" included in the RRC information element "ConfiguredGrantConfig" of the configured grant PUSCH.

[0020] TRI and TPMI may also be specified by the DCI's "Precoding information and number of layers" field. For simplicity, the "Precoding information and number of layers" field will also be referred to simply as the "Precoding field" hereafter.

[0021] The maximum number of layers (maximum rank) for UL transmission may also be set in the UE by the RRC parameter "maxRank".

[0022] The UE may report UE capability information regarding the precoder type, and the base station may set the precoder type based on this UE capability information via upper-layer signaling. This UE capability information may also be information about the precoder type used by the UE in PUSCH transmission (which may be represented by the RRC parameter "pusch-TransCoherence").

[0023] In this disclosure, the upper-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.

[0024] MAC signaling may use, for example, MAC Control Elements (MAC CEs) or MAC Protocol Data Units (PDUs). Broadcast information may also be, for example, Master Information Blocks (MIBs) or System Information Blocks (SIBs).

[0025] The UE may determine which precoder to use for PUSCH transmission based on precoder type information (which may be represented by the RRC parameter "codebookSubset") contained in the PUSCH configuration information (the "PUSCH-Config" information element of the RRC signaling) notified by higher-layer signaling. The UE may set a subset of the codebooks specified by TPMI using codebookSubset.

[0026] The precoder type may be specified by fully coherent, partially coherent, and non-coherent, or by a combination of at least two of these (for example, they may be represented by parameters such as "fullyAndPartialAndNonCoherent" or "partialAndNonCoherent").

[0027] Fully coherent may mean that all antenna ports used for transmission are synchronized (this may also be expressed as being able to align phases, using the same precoder, etc.). Partially coherent may mean that some of the antenna ports used for transmission are synchronized, but those ports are not synchronized with the others. Non-coherent may mean that the individual antenna ports used for transmission are not synchronized.

[0028] Furthermore, a UE that supports fully coherent precoder types may be assumed to support partially coherent and noncoherent precoder types. A UE that supports partially coherent precoder types may be assumed to support noncoherent precoder types.

[0029] The precoder type may be reinterpreted as coherency, push-transmit coherence, coherent type, coherence type, codebook type, codebook subset, codebook subset type, etc.

[0030] The UE may determine a precoding matrix from multiple precoders (which may also be called precoding matrices, codebooks, etc.) for CB-based transmissions that corresponds to the TPMI index obtained from the DCI (e.g., DCI format 0_1; hereafter the same) for scheduling UL transmissions.

[0031] Specifically, in Rel.15 / 16 NR, when using non-codebook-based transmission for PUSCH, the UE may have up to four SRS resources, with the non-codebook SRS resource set configured by the RRC, and one or more of these up to four SRS resources may be indicated by the DCI (2-bit SRI field).

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

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

[0034] Furthermore, the UE may be configured to use either codebook-based or non-codebook-based push transmission via a higher-layer parameter "txConfig" that indicates the transmission scheme. This parameter may represent the values ​​"codebook" or "noncodebook".

[0035] In this disclosure, codebook-based PUSCH (codebook-based PUSCH transmission, codebook-based transmission) may mean PUSCH when “codebook” is set as the transmission scheme for the UE. In this disclosure, non-codebook-based PUSCH (non-codebook-based PUSCH transmission, non-codebook-based transmission) may mean PUSCH when “non-codebook” is set as the transmission scheme for the UE.

[0036] Figures 1A and 1B show an example of a TPMI notification to a UE performing transmission for two antenna ports, where transform precoding is disabled and the maximum rank is set to 2.

[0037] Note that the presence of transform precoding may indicate the use of Discrete Fourier Transform spread OFDM (DFT-s-OFDM), while its absence may indicate the use of CP-OFDM.

[0038] This example shows the relationship (table) between the DCI precoding fields (shown as "bit fields mapped to the index" in the diagram; the same applies to similar diagrams thereafter) and TPMI (TPMI index) in Rel.15 NR. Note that "codebookSubset=fullyAndPartialAndNonCoherent" in Figure 1A indicates that it is a table referenced by a fully coherent UE, and "codebookSubset=nonCoherent" in Figure 1B indicates that it is a table referenced by a noncoherent UE.

[0039] The UE determines the number of layers to apply to the transmission and the TPMI for the precoding matrix based on the values ​​of the precoding fields included in the DCI and the table in Figure 1A / 1B. For example, a fully coherent UE with precoding field=2 will determine, based on Figure 1A, to use number of layers=2 and TPMI=0 for PUSCH transmissions. Note that "reserved" corresponds to a value that will be defined in the future.

[0040] Figure 2 shows an example of the correspondence between the TPMI index and the precoding matrix W. Figure 2 shows the precoding matrix W for two-layer transmission using two antenna ports with transform precoding disabled.

[0041] A UE that has decided to use layer count = 2 and TPMI = 0 for push transmission according to Figure 1A applies W, which corresponds to TPMI = 0 in Figure 2, to push transmission.

[0042] Furthermore, the UE may calculate block Z of complex symbol vectors for each antenna port that maps to a resource (e.g., a resource element) based on W and block Y of complex symbol vectors for each layer after transform precoding (or layer mapping). For example, it may be calculated as Z = WY.

[0043] In the existing Rel.15 / 16 NR specification, for codebook-based transmissions, W is specified by the TPMI indicated by the precoding field as described above, while for non-codebook-based transmissions, W is specified as the identity matrix.

[0044] In Figure 2, for W, Layer 1 (the column vector in the first column) and Layer 2 (the column vector in the second column) have the same power. For example, for TPMI=0, the sum of the squares of each component of the column vector in Layer 1 and the sum of the squares of each component of the column vector in Layer 2 are both 1 / 2 (=(1 / √2)^2), and the power ratio between Layer 1 and Layer 2 is 1:1.

[0045] As shown above, in existing Rel.15 / 16 NR systems, when transmitting channels / signals using multiple antenna ports, control is implemented to ensure equal power between antenna ports and to apply equal power / the same modulation and coding scheme (MCS) across layers.

[0046] Furthermore, the same control is applied not only to uplink transmissions (e.g., PUSCH) but also to downlink transmissions (e.g., Physical Downlink Shared Channel (PDSCH)).

[0047] However, future wireless communication systems (such as 6G) will require faster communication in a Multi Input Multi Output (MIMO) environment. However, how to achieve this high speed has not yet been thoroughly investigated. Failure to clarify this could hinder the increase in communication throughput.

[0048] Therefore, the inventors devised a method for appropriately controlling power / MCS for each layer / port. This method allows for optimal power allocation for each transmission line (layer) based on the water injection theorem, and is expected to increase communication line capacity.

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

[0050] In this disclosure, "A / B" may mean "at least one of A and B."

[0051] In this disclosure, the upper-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.

[0052] MAC signaling may use, for example, MAC Control Elements (MAC CEs) or MAC Protocol Data Units (PDUs). Broadcast information may also include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), or Other System Information (OSIs).

[0053] Physical layer signaling may include, for example, Downlink Control Information (DCI).

[0054] In this disclosure, the terms activate, deactivate, indicate, select, configure, update, determine, etc., may be interpreted interchangeably.

[0055] In this disclosure, the terms used include: panel, beam, panel group, beam group, Uplink (UL) transmit entity, TRP, spatial relation information (SRI), spatial relation, 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 relation group, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state (unified TCI state). The terms (state), QCL, etc., may be interpreted interchangeably.

[0056] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interpreted as mutually exclusive. "Spatial relationship information" may be interpreted as mutually exclusive as "a set of spatial relationship information," "one or more spatial relationship information," etc. TCI state and TCI may be interpreted as mutually exclusive.

[0057] In this disclosure, the terms index, ID, indicator, and resource ID may be interpreted interchangeably. Similarly, in this disclosure, the terms sequence, list, set, group, cluster, subset, etc., may be interpreted interchangeably.

[0058] In the following description of the embodiments, "Spatial Relation Information (SRI)", "Spatial Relation Information for PUSCH", "Spatial Relationship", "UL Beam", "UE Transmit Beam", "UL TCI", "UL TCI State", "Spatial Relationship of UL TCI State", SRS Resource Indicator (SRI)", SRS Resource, Precoder, etc. may be interpreted as one another.

[0059] In this disclosure, layers, ports (antenna ports), SRS ports, DMRS ports, etc., may be interpreted interchangeably. For example, the power ratio between layers may be interpreted as the power ratio between ports.

[0060] Furthermore, layers may be interpreted as a group of one or more layers (layer group), a group of one or more of the above-mentioned ports (port group), and so on. For example, layers 1 and 2 may be treated as belonging to layer group 1, and layer 3 may be treated as belonging to layer group 2.

[0061] In this disclosure, "layer i" (where i is an integer) may be interpreted as layer i-1, layer i+1, or any other layer number (i.e., any layer number).

[0062] In the following embodiments, "PUSCH" may be replaced with other UL channel / UL signals (e.g., PUCCH, DMRS, SRS).

[0063] In the following embodiments, "PDSCH" may be replaced with other DL channel / DL signals (e.g., PDCCH, DMRS, CSI-RS).

[0064] In the following embodiments, "power" may be interpreted as "transmit power" and may mean PUSCH transmit power, PDSCH transmit power, etc. Also, in this disclosure, power may be interpreted as at least one of the following: the absolute value of a precoding vector / matrix, the sum of the squares of all elements in a particular column (or row) of the vector / matrix, or the sum of the squares of all elements in the vector / matrix.

[0065] (Wireless communication method) <First Embodiment> The first embodiment relates to power control of PUSCH for each layer.

[0066] In the first embodiment, the UE may transmit the PUSCH using different power levels for each layer.

[0067] Figure 3 shows a conceptual diagram of the first embodiment. As described above, in Rel.15 / 16 NR, the UE equally distributed power between layers, but in the first embodiment, as shown, Layer 1 can be transmitted with high transmission power and Layer 2 with low transmission power.

[0068] The UE may determine (or be able to determine) the per-layer push power if at least one of the following conditions is met: Condition 1-1: The UE reports that it can (or supports) power control of each layer of the pusher. Condition 1-2: The UE is configured to have specific higher-level parameters set. Conditions 1-3: The UE receives a specific MAC CE, Conditions 1-4: The number of layers in the PUSCH is a certain value / falls within a certain range. Conditions 1-5: For the PUSCH in question, the MCS for each layer is specified.

[0069] The report for condition 1-1 may also be a report of UE capability information indicating support for PUSCH power control on a per-layer basis.

[0070] The higher-layer parameter in condition 1-2 may be a parameter indicating that power control of the PUSCH per layer is enabled. This parameter may be a parameter included in the PUSCH configuration information (e.g., the PUSCH-config information element). This parameter may be, for example, a parameter for full power transmission power (e.g., ul-FullPowerTransmission).

[0071] The MAC CE for conditions 1-3 may be a MAC CE indicating the activation / deactivation of per-layer pusher power control. If per-layer pusher power control is activated, the UE may perform per-layer pusher power control; if deactivated, it may not perform per-layer pusher power control (in this case, it may perform layer-common pusher power control as specified in Rel. 15 / 16 NR).

[0072] The "certain value" in conditions 1-4 could be, for example, 1, 2, 4, 8, etc. The "included in a certain range" in conditions 1-4 could also mean "greater than or equal to a threshold," "less than or equal to a threshold," etc.

[0073] The "certain values" and "certain ranges" (e.g., the thresholds mentioned above) in conditions 1-4 may be predetermined by the specifications, specified based on higher layer signaling (e.g., RRC parameters, MAC CE), physical layer signaling (e.g., DCI), or a combination thereof, or determined based on UE capabilities.

[0074] Conditions 1-5 may be assumed to be satisfied, for example, if the DCI that schedules PUSCH contains multiple MCS fields, each indicating a different layer's MCS, or if it contains a single MCS field indicating multiple MCSs for each of the multiple layers.

[0075] The first embodiment can be broadly divided into two types depending on how the UE determines the PUSCH transmit power for each layer: • Embodiment 1.1: Determined by the UE based on DCI, Embodiment 1.2: Determined by the UE based on RRC parameters.

[0076] Embodiments 1.1 and 1.2 may be applied if at least one of the above conditions 1-1 to 1-5 is met. For example, the table in Figure 4A / 4B in Embodiment 1.1.1, described later, may be referenced by the UE only if at least one of the above conditions 1-1 to 1-5 is met. Also, for example, the power ratio field in Embodiment 1.1.3, described later, may be assumed by the UE to be included in the DCI only if at least one of the above conditions 1-1 to 1-5 is met.

[0077] In this disclosure, the following embodiments show an example in which the power for each layer is determined based on the power ratio between layers, but the power ratio may be interpreted as the transmit power value of each layer. In this case, one of the transmit power values ​​of each layer may be given to the UE, and the transmit power values ​​of the other layers may be determined based on this.

[0078] The power ratio between layers may be given as power ratio = (1, 1) (which may mean that the power (power coefficient) of layer 1 : the power of layer 2 = 1:1; the same applies hereafter), or it may be given by a diagonal matrix in which the diagonal elements are the power ratio values ​​for each layer (for example, the diagonal element in row i, column i represents the power (power coefficient) of layer 1). Hereafter, this diagonal matrix will also be called the power distribution matrix R (a matrix representing the power for each layer).

[0079] The power distribution matrix R may be derived from the power ratio between layers given as power ratio = (1, 1), or conversely, the power ratio between layers may be derived from R. In the following embodiments, the power ratio and the power distribution matrix R may be interchangeable.

[0080] [Embodiment 1.1] The UE may determine the power per layer based on the fields included in the DCI.

[0081] For example, the UE may determine the power ratio between layers or the transmit power value of each layer based on one or a combination thereof of the precoding information and number of layers field (hereinafter also referred to as the precoding field for simplicity), the SRI field, etc.

[0082] Embodiment 1.1 is further broadly divided into Embodiments 1.1.1 to 1.1.3.

[0083] [[Implementation 1.1.1]] In Embodiment 1.1.1, the UE determines the TPMI and power ratio based on the value of the precoding field. That is, in Embodiment 1.1.1, at least one code point in the precoding field is associated with the power ratio.

[0084] In Embodiment 1.1.1, the UE may calculate the above-mentioned Z based on the precoding matrix W corresponding to TPMI, the above-mentioned Y, and the power distribution matrix R. For example, Z may be obtained as Z = WRY.

[0085] Figures 4A and 4B show an example of a TPMI notification to a UE transmitting for two antenna ports in Embodiment 1.1.1, where transform precoding is disabled and the maximum rank is set to 2. In this example, the same points as in Figures 1A and 1B will not be repeated.

[0086] In this example, if the number of layers associated with a code point (value) in the precoding field is two or more, the code point is associated not only with the number of layers and TPMI, but also with the power ratio between layers. For example, in Figure 4A, code point = 2 indicates a power ratio of (1, 1), and code point = 8 indicates a power ratio of (2 / √3, √2 / √3).

[0087] For TPMIs with the same number of layers but different power ratios (code points 2 and 7 in Figure 4A), the same / different power ratios may be specified, or for the same TPMI with the same number of layers (code points 7 and 8 in Figure 4A), the same / different power ratios may be specified.

[0088] In Embodiment 1.1.1, the number of bits in the precoding field may vary depending on whether or not layer-specific power control is performed. In other words, the UE may assume that the number of bits in the precoding field when layer-specific power control is performed is different from or the same as the number of bits in the precoding field when layer-specific power control is not performed.

[0089] The power ratios associated with each code point may be predetermined by the specifications, or they may be specified / determined by upper-layer signaling, physical layer signaling, UE capability, or a combination thereof.

[0090] [[Embodiment 1.1.2]] In Embodiment 1.1.2, the UE determines the TPMI based on the value of the precoding field, similar to existing standards. However, it differs from existing standards in that the W corresponding to the TPMI includes W adjusted so that the power ratio for each layer is different.

[0091] In Embodiment 1.1.2, the UE may calculate the above-mentioned Z based on the precoding matrix W corresponding to TPMI (considering the power ratio between layers) and the above-mentioned Y. For example, it may be obtained as Z = WY.

[0092] Figure 5 shows an example of the correspondence between the TPMI index and the precoding matrix W in Embodiment 1.1.2. Similar to Figure 2, Figure 5 shows the precoding matrix W for two-layer transmission using two antenna ports with transform precoding disabled, but assuming that W is the same between the layers in Figure 2, TPMI If we set it as follows, then by the power distribution matrix R, W=W TPMI This corresponds to an example expressed in R.

[0093] Furthermore, in this disclosure, WR or W TPMI Examples of R such that the sum of the squares of all components of R is 1 or less are shown, but R such that the sum of the squares is greater than 1 may also be permitted.

[0094] As shown in Figure 5, different W TPMI Regarding this, W may be available that is multiplied by the same / different R, or the same W TPMI Regarding this, a different R multiplied by W may be available.

[0095] As with other drawings, indices that are not shown may simply be omitted (for example, they may be assigned the letter W), or they may be marked as Reserved.

[0096] In Embodiment 1.1.2, the number of bits in the precoding field may vary depending on whether or not layer-specific power control is performed. In other words, the UE may assume that the number of bits in the precoding field when layer-specific power control is performed is different from or the same as the number of bits in the precoding field when layer-specific power control is not performed.

[0097] The W corresponding to the TPMI index may be predetermined by the specification, or it may be specified / determined by upper-layer signaling, physical layer signaling, UE capability, or a combination thereof.

[0098] [[Implementation 1.1.3]] In Embodiment 1.1.3, the UE determines the power ratio based on the value of a specific field in the DCI or the value of a specific index indicated by the value of a specific field.

[0099] In Embodiment 1.1.3, the UE may calculate the above-mentioned Z based on the precoding matrix W corresponding to TPMI, the above-mentioned Y, and the power distribution matrix R. For example, it may be obtained as Z = WRY.

[0100] The specific field in Embodiment 1.1.3 may be at least one of the following: for example, a precoding field, an SRI field, a time / frequency resource allocation field, and the specific index may be at least one of the following: a TPMI index, an SRI index (SRI).

[0101] Figures 6A and 6B show an example of the correspondence between an index and the power distribution matrix R in Embodiment 1.1.3. In Figure 6A, R is associated with the TPMI index derived based on the precoding field. In Figure 6B, R is associated with the value of the SRI field. Note that R may be determined based on one or more SRIs corresponding to the value of the SRI field.

[0102] Furthermore, the specific field in Embodiment 1.1.3 may be a new field not defined in existing NRs, which indicates the power ratio (or R) between layers (for example, referred to as the power ratio field).

[0103] In Embodiment 1.1.3, the number of bits in the power ratio field may be determined based on at least one of the following: the number of layers, the upper layer parameters, etc.

[0104] The power ratio associated with each code point in the power ratio field may be predetermined by the specifications, or it may be specified / determined by upper-layer signaling, physical layer signaling, UE capability, or a combination thereof.

[0105] [Embodiment 1.2] The UE may determine the power for each layer based on the RRC parameters.

[0106] In Embodiment 1.2, as shown in the above embodiment, Z is set to Z=WRY or Z=WY=W TPMI It may also be calculated based on RY. This R (or WR or W TPMI R) may be determined based on the RRC parameter.

[0107] Figure 7 shows an example of RRC information elements / parameters for setting the power ratio according to Embodiment 1.2. This example is written using Abstract Syntax Notation One (ASN.1) notation (however, this is merely an example and may not be a complete description). In this drawing, RRC information elements / parameters with the same names as those already specified in the Rel. 15 / 16 NR specification (TS 38.331) will be understood by those skilled in the art.

[0108] In this disclosure, the names of RRC information elements, RRC parameters, etc., are not limited to those mentioned above. For example, suffixes indicating that they were introduced in a specific resource (e.g., "_r18", "-r18", etc.) may be added. Such suffixes are optional, or other words may be added.

[0109] In this example, the RRC information element "ConfiguredGrantConfig" of the configured grant PUSCH is shown.

[0110] For example, enablePowerDistributionPerLayer might be a parameter that enables (if enabled) per-layer power control.

[0111] The UE may determine the power ratio of the configured grant PUSCH by using the value provided by precodingAndNumberOfLayers in the RRC-ConfiguredUplinkGrant instead of the DCI precoding field. The above can be applied with modifications in Embodiments 1.1.1, 1.1.2, etc.

[0112] The UE may determine the power ratio of the configured grant PUSCH by using the value provided by powerDistributionPerLayer in the RRC-ConfiguredUplinkGrant instead of the DCI power ratio field. The above can be applied with modifications in Embodiment 1.1.3. Note that powerDistributionPerLayer may represent an index associated with a power ratio (an integer between 0 and 15 in the figure), or it may represent an array / resource / sequence containing values ​​for one or more power ratios (for example, power ratio values ​​for Layer 1 and Layer 2).

[0113] Note that the setting of RRC parameters related to the power ratio, as shown in Figure 7, is not limited to ConfiguredGrantConfig, but may also be set in, for example, PUSCH configuration information (PUSCH-Config information element). In this case, each of the above parameters may be considered to be a parameter for controlling PUSCH, and for example, the UE may determine the power ratio for dynamic PUSCH scheduled by DCI based on the RRC parameters related to the power ratio included in the PUSCH configuration information.

[0114] [Modified version of the first embodiment] The power ratio determination methods of Embodiments 1.1 and 1.2 described above may be applied to codebook-based transmission or to non-codebook-based transmission.

[0115] In non-coded book-based transmission, W may remain the existing identity matrix and Z may be calculated as Z=WRY based on the determined power ratio (power distribution matrix R). Alternatively, in non-coded book-based transmission, W may be the power distribution matrix R and Z=RY may be calculated. For non-coded book-based transmission, W in the above embodiment may be replaced with the existing identity matrix or R.

[0116] Figure 8 shows an example of applying the power ratio to non-coded book-based transmission in the first embodiment. In this example, it is assumed that a UE configured for non-coded book-based transmission is shown two SRI indices (SRI1, SRI2) by the SRI field of the DCI.

[0117] The UE may, in accordance with Embodiment 1.1.3, further determine the power ratio based on the value of the SRI field (for example, layer (port) 1:2 = (2 / √3, √2 / √3)) and transmit by applying the respective power ratios to the two SRIs indicated by the two SRI indices.

[0118] The UE may assume that any of the power ratio determination methods described in Embodiments 1.1 and 1.2 above can be applied to codebook-based transmission.

[0119] The UE may assume that, for non-codebook-based transmissions, a method for determining the power ratio that is not based on the precoding field (or TPMI) (e.g., the powerDistributionPerLayer-based method in Embodiment 1.1.3 and Embodiment 1.2) may be applicable.

[0120] According to the first embodiment described above, power control for each layer can be appropriately implemented.

[0121] <Second Embodiment> The second embodiment relates to MCS control of PUSCH for each layer.

[0122] In the second embodiment, the UE may apply a different MCS to each layer and transmit the PUSCH. When the UE applies a different MCS to each layer, it may use these different MCSs to calculate the Transport Block Size (TBS) transmitted in the PUSCH. For example, the UE may calculate the TBS for each layer using its respective MCS. In this case, the total TBS transmitted using multiple layers may be calculated as the sum of the TBS for each layer. This will be discussed later.

[0123] Figure 9 shows a conceptual diagram of the second embodiment. As described above, in Rel.15 / 16 NR, the UE applied the same MCS across layers, but in the second embodiment, as shown, Layer 1 can be transmitted using an MCS with a low code rate (e.g., MCS index = 0), and Layer 2 can be transmitted using an MCS with a high code rate (e.g., MCS index = 5).

[0124] The UE may decide to make (or be able to make) a layer-by-layer MCS decision for PUSCH if at least one of the following conditions is met: Condition 2-1: The UE reports that it can (or supports) controlling the MCS on a per-layer basis. Condition 2-2: The UE is configured to have specific higher-level parameters set. Condition 2-3: The UE receives a specific MAC CE, Condition 2-4: The number of layers in the PUSCH is a certain value / falls within a certain range. Condition 2-5: For the PUSCH in question, different power levels are applied to each layer (different power ratios are specified / set).

[0125] The report for condition 2-1 may also be a report of UE capability information indicating support for PUSCH's MCS control on a per-layer basis.

[0126] The higher-layer parameter in condition 2-2 may be a parameter indicating that MCS control of the PUSCH per layer is enabled. This parameter may be a parameter included in the PUSCH configuration information (e.g., the PUSCH-config information element). This parameter may be, for example, a parameter for full power transmission power (e.g., ul-FullPowerTransmission).

[0127] The MAC CE in condition 2-3 may be a MAC CE indicating activation / deactivation of layer-specific push MCS control. If layer-specific push MCS control is activated, the UE will perform layer-specific push MCS control; if deactivated, it does not need to perform layer-specific push MCS control (in this case, it may perform layer-common push MCS control as specified in Rel.15 / 16 NR).

[0128] The "certain value" in condition 2-4 could be, for example, 1, 2, 4, 8, etc. The "included in a certain range" in condition 2-4 could also mean "greater than or equal to a threshold," "less than or equal to a threshold," etc.

[0129] The "certain value" and "certain range" (e.g., the threshold mentioned above) in condition 2-4 may be predetermined by the specifications, specified based on higher layer signaling (e.g., RRC parameters, MAC CE), physical layer signaling (e.g., DCI), or a combination thereof, or determined based on UE capabilities.

[0130] Conditions 2-5 may be assumed to be satisfied, for example, when the power ratio shown in the first embodiment is specified / set.

[0131] The second embodiment can be broadly divided into two types depending on how the UE determines the MCS of each layer of PUSCH: • Embodiment 2.1: Determined by the UE based on DCI, Embodiment 2.2: Determined by the UE based on RRC parameters

[0132] Embodiments 2.1 and 2.2 may be applied if at least one of the above conditions 2-1 to 2-5 is met. For example, the MCS table in Embodiment 2.1, described later, may be referenced by the UE only if at least one of the above conditions 2-1 to 2-5 is met. Also, for example, the second MCS field or MCS offset field in Embodiment 2.1, described later, may be assumed by the UE to be included in the DCI only if at least one of the above conditions 2-1 to 2-5 is met.

[0133] [Embodiment 2.1] The UE may determine the MCS for each layer based on the fields included in the DCI.

[0134] For example, a UE may determine the MCS for each of multiple layers based on a single MCS field. This MCS field may be represented with the same number of bits (5 bits) as an existing MCS field, or with a different number of bits (e.g., more bits). If a single MCS field identifies the MCS indices of multiple layers, this MCS field may be called an MCS group field, for example.

[0135] The UE may determine the MCS index of other layers based on the MCS index of one layer indicated by the one MCS field described above.

[0136] Furthermore, the UE may determine the MCS of one layer for each MCS field based on multiple MCS fields. This MCS field may be represented with the same number of bits (5 bits) as an existing MCS field, or with a different number of bits (e.g., fewer bits).

[0137] In Embodiment 2.1, the number of bits in each MCS field may vary based on at least one of the following: whether or not layer-specific MCS control is performed, and the number of transmission layers. For example, the UE may assume that the number of bits in the MCS field when layer-specific MCS control is performed is different from or the same as the number of bits in the MCS field when layer-specific MCS control is not performed.

[0138] Figures 10A and 10B show an example of determining the MCS for each layer based on the MCS field in Embodiment 2.1.

[0139] Figure 10A shows an example where multiple MCS fields included in DCI indicate the MCS for different layers. In this example, the first MCS field indicates the MCS index (=3) for layer 1, and the second MCS field indicates the MCS index (=4) for layer 2.

[0140] Figure 10B shows an example where one MCS field in the DCI indicates the MCS of one layer. In this example, one MCS field indicates the MCS index (=3) for layer 1. The UE may determine the MCS index for layer 2 as the MCS index for layer 1 + 1 (=4).

[0141] When determining the MCS index of another layer based on the MCS index of one layer indicated by one MCS field, the MCS index of the other layer may be calculated as: MCS index of one layer + MCS offset (in Figure 10B above, MCS offset = 1). The MCS offset may be interpreted interchangeably with the MCS index offset, differential MCS index, etc. The MCS offset may be an integer or take a negative value.

[0142] The single MCS field mentioned above may indicate the MCS index of the smallest index layer (e.g., Layer 1) or the largest index layer (e.g., the highest rank layer).

[0143] The MCS offset may be predetermined by specification, or it may be specified / determined by upper-layer signaling, physical layer signaling, UE capability, or a combination thereof. The MCS offset may be specified by an MCS offset field included in the same DCI as the MCS field. The number of bits in the MCS offset field may be determined based on at least one of the following: the number of layers, upper-layer parameters, etc.

[0144] Figures 11A and 11B show an example of determining the MCS for multiple layers according to Embodiment 2.1. Figure 11A shows the MCS field (MCS index I) which is also used in the existing Rel.15 / 16 NR. MCS This shows the correspondence between the parameters (modulation order Qm, target coding rate R, and spectral efficiency).

[0145] A table showing such correspondences may be called an MCS table or MCS index table. The modulation order is a value corresponding to the modulation scheme. For example, the modulation orders for QPSK (Quadrature Phase Shift Keying), 16QAM (Quadrature Amplitude Modulation), 64QAM, and 256QAM may be 2, 4, 6, and 8, respectively.

[0146] Consider the case where the UE specifies the MCS index of Layer 1 = 7 by one of the MCS fields in the DCI. The UE may also specify the MCS index of Layer 2 by the MCS offset field included in the same DCI. Figure 11B shows an example of the correspondence between the MCS offset field and the MCS parameter for Layer 2 in this case. The MCS parameter in Figure 11B corresponds to the MCS parameter corresponding to the MCS index = 4-7 in Figure 11A. In other words, in this example, the values ​​of the MCS offset field = 0, 1, 2, and 3 correspond to MCS offsets = -3, -2, -1, and 0, respectively.

[0147] The correspondence between the value of the MCS offset field and the MCS offset (or MCS parameter) may be specified / determined by upper-layer signaling, physical layer signaling, UE capability, or a combination thereof.

[0148] Specifying the MCS for multiple layers using the MCS field and the MCS offset field is expected to result in MCS notification with fewer bits (lower overhead) than specifying the MCS for multiple layers using two MCS fields.

[0149] [[MCS Table]] In Figure 11A above, an MCS table is shown where one value of the MCS index corresponds to the MCS of one layer. However, an MCS table where one value of the MCS index corresponds to the MCS of multiple layers may be used. In this case, the UE may determine the MCS of multiple layers from a single MCS field, without relying on the MCS offset described above.

[0150] Figure 12 shows an example of an MCS table where a single value in the MCS index corresponds to the MCS parameters of multiple layers. In this example, the MCS parameters of Layer 0 and Layer 1 are associated with the MCS index.

[0151] Note that, instead of referencing a single MCS table showing the MCS for multiple layers as shown in Figure 12, multiple MCS tables showing the MCS for separate layers may be referenced. For example, when a UE schedules a 2-layer transmission, it may determine the MCS for Layer 0 based on the MCS field and a first table (an MCS table for the MCS parameters of Layer 0), and then determine the MCS for Layer 1 based on the same MCS field and a second table (an MCS table for the MCS parameters of Layer 1).

[0152] The UE may determine which MCS table to reference based on the number of layers in the PUSCH being sent.

[0153] Furthermore, when determining the MCS of one layer for each MCS field, or when determining the MCS of multiple layers for each MCS field, or both, the UE may determine the layer-specific MCS parameters by referring to the same (common) MCS table for each layer, or by referring to different MCS tables for each layer.

[0154] The MCS table referred to for a certain layer may be determined in advance according to the specifications, or may be specified / determined by upper-layer signaling, physical-layer signaling, UE capabilities, or a combination thereof. For example, RRC parameters for specifying the MCS table to be referred to for each layer may be set.

[0155] [[TBS]] The calculation of the total TBS received using multiple layers in the second embodiment will be described.

[0156] In the existing Rel.15 / 16 NR specifications, the UE calculates the TBS for PUSCH based on the following steps S101 - S103.

[0157] In step S101, the UE determines the total number of resource elements (RE) (N RE ) allocated to the PUSCH within a slot based on the number of RE (N’ RE ) allocated to the PUSCH within one physical resource block (PRB).

[0158] In step S102, the UE determines an unquantized intermediate variable (N info ). Specifically, N info may be obtained by N info = N RE ·R·Qm·ν. Here, R and Qm are the target coding rate and modulation order determined based on the MCS field (MCS index (I MCS )) of the DCI and the MCS table, respectively. Also, ν is the number of layers of the PDSCH.

[0159] In step S103, the UE determines the TBS based on the above N info . Note that according to the value of N info (for example, N infoThe intermediate variable (N') is quantized in different ways depending on whether the value is below the threshold (=3824). info ) is derived, and N' info Based on this, TBS may make the decision.

[0160] Now, in the second embodiment, for calculating the total TBS received using multiple layers, a step that modifies at least one of the above steps S101-S103 may be used.

[0161] For example, in step S102, N info is, N info =Σ ν i=1 (N RE ·R i Qm i ) can also be calculated using R. i and Qm i These may be the target coding rate and modulation order for layer i, respectively. Σ ν i=1 (N RE ·R i Qm i ) represents N from i=1 to i=ν RE ·R i Qm i It may also mean the sum of N. In this case, this N info The TBS determined in step S103 based on this will be the result of considering the MCS for each layer.

[0162] Also, for example, in step S102, N for layer i info、i However, N info、i =N RE ·R i Qm i It is determined by, and in step S103, similar to the existing method, N info、i TBS is based on Layer i. i The TBS for all layers is determined to be TBS = Σ ν i=1 TBS iThis may be determined by the following. This TBS is the result of considering the MCS for each layer. Note that N info、i Based on this, the quantized intermediate variable (N') for layer i. info、i ) is derived, and N' info、i If TBS makes a decision based on the above N' info Based on a threshold value different from the threshold (=3824) used to determine the method for determining (and TBS), the above N' info、i (and TBS) i The method for determining the threshold may be determined. Also, this threshold may be a different value for each layer i (threshold). i ) may also be. Each threshold i This may be predetermined by the specifications, or it may be specified / determined by upper-layer signaling, physical layer signaling, UE capabilities, or a combination thereof.

[0163] In these modified steps, the total number of REs assigned to PUSCH in each layer's slot is N. RE、i When expressed as above, N RE is N RE、i It can also be reinterpreted as follows.

[0164] For example, the UE may determine the modulation order (Qm1) and target coding rate (R1) for Layer 1 based on the MCS index for Layer 1 (for example, given from the first MCS field), and determine the modulation order (Qm2) and target coding rate (R2) for Layer 2 based on the MCS index for Layer 2 (for example, given from the second MCS field, or from the first MCS field and the MCS offset field).

[0165] [Embodiment 2.2] The UE may determine the MCS for each layer based on the RRC parameters.

[0166] Figure 13 shows an example of RRC information elements / parameters for setting the MCS for each layer according to Embodiment 2.2. This example is similar to Figure 7, and the same explanations as in Figure 7 will not be repeated.

[0167] For example, enableMCSPerLayer could be a parameter that enables (if enabled) MCS control for each layer.

[0168] The UE may use the value provided by mcsAndTBS in the RRC-ConfiguredUplinkGrant instead of the DCI's MCS field to determine the MCS for each layer of the configured grant PUSCH.

[0169] The UE may use the values ​​provided by mcsAndTBSForLayer0 and mcsAndTBSForLayer1 in the RRC-ConfiguredUplinkGrant instead of the first and second MCS fields of the DCI in Embodiment 2.1 to determine the MCS for Layer 0 and Layer 1 of the configured grant PUSCH, respectively.

[0170] Furthermore, if at least one of mcsAndTBS, mcsAndTBSForLayer0, and mcsAndTBSForLayer1 is set, the UE may derive a layer-specific TBS for the configured grant PUSCH based on the layer-specific MCS.

[0171] Note that the setting of RRC parameters for each layer MCS as shown in Figure 13 is not limited to ConfiguredGrantConfig, but may also be set in, for example, PUSCH configuration information (PUSCH-Config information element). In this case, the UE may determine that each of the above parameters is a parameter for controlling PUSCH, and may, for example, determine the layer-specific MCS for dynamic PUSCH scheduled by DCI based on the RRC parameters for each layer MCS included in the PUSCH configuration information.

[0172] [Modified version of the second embodiment] Multiple MCSs applied to multiple layers may be assumed to be unconstrained (any combination may be used; for example, any combination of different modulation orders may be applied between layers), or they may be assumed to be constrained. For example, there may be a constraint that the modulation order applied to the first layer is the same as the modulation order applied to the second layer, or that the difference between these orders is less than or equal to a threshold (e.g., 2). Alternatively, there may be a constraint that the target coding rate applied to the first layer is the same as the target coding rate applied to the second layer, or that the difference between these is less than or equal to a threshold (e.g., 200).

[0173] Such constraints may be predetermined by specifications, or they may be specified / determined by upper-layer signaling, physical layer signaling, UE capabilities, or a combination thereof.

[0174] According to the second embodiment described above, MCS control can be appropriately implemented for each layer.

[0175] <Further modifications of the first and second embodiments> [Power and MCS control per layer] Layer-by-layer power control according to the first embodiment and layer-by-layer MCS control according to the second embodiment may be performed simultaneously. In this case, both the layer-by-layer power ratio and MCS may be controlled based on a specific field of the DCI.

[0176] The specific field in question may be a field defined in existing DCIs, such as a precoding field, SRI field, or MCS field, or it may be a newly defined field.

[0177] Figure 14 shows an example of determining the layer-by-layer power ratio and MCS based on a specific field in a modified version of the first and second embodiments.

[0178] In this example, the value of a specific field (DCI field) is associated with the power per layer (power distribution matrix R) and the MCS index per layer. The correspondence between the value of the specific field and R and the MCS index (or MCS parameter) may be predetermined by the specification, or it may be specified / determined by upper-layer signaling, physical layer signaling, UE capability, or a combination thereof.

[0179] The MCS for each layer may be associated with the value of the DCI field, as shown in Figure 14 where the DCI field value is 0 or 1, or it may be associated with the value of the DCI field and the value of another field (e.g., the MCS field), as shown in Figure 14 where the DCI field value is 2. In the example of the DCI field value = 2 in Figure 14, the MCS index for layer 1 and the MCS index for layer 2 are determined by adding different values ​​(3 and 2) to the MCS index obtained from the MCS field, respectively.

[0180] The first value of the specific field mentioned above (for example, 0) may indicate that neither layer-specific power control nor MCS control will be performed. UEs to which this value is specified may perform power control and MCS control for PUSCH transmissions in a layer-wide manner, similar to Rel.15 / 16 NR.

[0181] Furthermore, a second value (e.g., 1) of the above-mentioned specific field may indicate that layer-specific MCS control is performed but layer-specific power control is not. Also, a third value (e.g., 2) of the above-mentioned specific field may indicate that layer-specific power control is performed but layer-specific MCS control is not.

[0182] [Power / MCS control per TRP in MTRP PUSCH] The layer-by-layer power / MCS control in the first and second embodiments may be applied to the power / MCS control per TRP in a PUSCH (MTRP PUSCH) for multiple transmission / reception points (TRPs) (multi-TRPs (MTRPs)).

[0183] In future wireless systems (e.g., NR Rel.17 and later), it is being considered to use a single DCI to instruct multiple (e.g., two) SRI / TPMIs for repeated push transmission of multiple TRPs (MTRP push repetition). Such operation may be called single-DCI (s-DCI) based multi-TRP operation.

[0184] When a single DCI (sDCI) points to multiple SRI / TPMIs, the following options 1 or 2 are possible: Option 1: Use a field to indicate multiple (e.g., two) SRI / TPMI values ​​for multiple (e.g., two) TRPs. Option 2: A field is designated to indicate one SRI / TPMI, and that field is set with code points corresponding to multiple (e.g., two) SRI / TPMI values.

[0185] In Option 1, each code point of multiple SRI / TPMI fields may correspond to a single TPMI value. The correspondence (association) between SRI / TPMI fields and SRI / TPMI values ​​may be defined in advance in the specification. Alternatively, the correspondence (association) between SRI / TPMI fields and SRI / TPMI values ​​may use the correspondences defined up to Rel. 16, or the correspondences defined in Rel. 17 or later. The correspondence between SRI / TPMI fields and SRI / TPMI values ​​may differ for each of the multiple SRI / TPMI fields.

[0186] In Option 2, a code point that points to one SRI / TPMI field may correspond to multiple (e.g., two) SRI / TPMI values. The correspondence (association) between SRI / TPMI fields and SRI / TPMI values ​​may be defined in advance in the specification, or it may be notified / configured / activated by RRC signaling / MAC CE.

[0187] Now, if sDCI specifies multiple RSs (e.g., SRSs) (in other words, multiple SRIs), the UE may apply a different transmit power / MCS for each PUSCH transmit corresponding to each specified RS.

[0188] For example, if the sDCI detected by the UE contains multiple SRI fields, the UE will send multiple PUSCHs using the SRS ports corresponding to the SRS resources specified by these fields. In this case, the UE may send these multiple PUSCHs with different power / MCS applied to each PUSCH.

[0189] This control may be implemented by embodiments in which, in the first / second embodiments described above, “layer” is reinterpreted as at least one of the following: “TRP,” “RS (e.g., SRS),” “PUSCH transmit corresponding to RS,” “PUSCH,” or “a group consisting of one or more PUSCH transmits corresponding to RS (a group including one or more PUSCH transmits corresponding to RS).” For example, the power ratio per layer may be applied to each PUSCH individually, rather than being multiplied by a precoding matrix for a single PUSCH.

[0190] Figure 15 shows an example of per-push power control for an MTRP pusher based on a further modification of the first embodiment. For example, consider a case where BS1 notifies the UE of an sDCI to schedule an MTRP pusher, which includes a first SRI field indicating SRS1, a second SRI field indicating SRS4, and information indicating the per-pusher power ratio.

[0191] In this case, the UE may transmit using high power for SRS1 (and the corresponding PUSCH for SRS1) (for BS1) and low power for SRS4 (and the corresponding PUSCH for SRS4) (for BS2), as shown in Figure 15.

[0192] Figure 16 shows an example of per-push MCS control for an MTRP PUSCH based on a further modification of the second embodiment. For example, consider a case where BS1 notifies the UE of an sDCI to schedule an MTRP PUSCH, which includes a first SRI field indicating SRS1, a second SRI field indicating SRS4, and information indicating the per-push MCS.

[0193] In this case, the UE may apply a low MCS index to SRS1 (and the corresponding PUSCH for SRS1) (for BS1) and a high MCS index to SRS4 (and the corresponding PUSCH for SRS4) (for BS2), as shown in Figure 16.

[0194] <Third Embodiment> The third embodiment relates to MCS control of PDSCH for each layer.

[0195] In a third embodiment, the UE may receive the PDSCH by applying a different MCS for each layer (DMRS port) for a single codeword. When the UE applies a different MCS for each layer, it may use these different MCSs to calculate the Transport Block Size (TBS) received by the PDSCH. For example, the UE may calculate the TBS for each layer using its respective MCS. In this case, the total TBS received using multiple layers may be obtained by summing the TBS for each layer.

[0196] Figure 17 shows a conceptual diagram of the third embodiment. As described above, in Rel.15 / 16 NR, the UE applied the same MCS across layers, but in the third embodiment, the UE can receive Layer 1 based on an MCS with a high code rate and Layer 2 based on an MCS with a low code rate, as shown in the figure.

[0197] The third embodiment may be implemented as an embodiment that appropriately modifies the second embodiment described above. For example, the third embodiment may correspond to an embodiment in the second embodiment in which "PUSCH" is read as "PDSCH", "(PUSCH) transmission" is read as "(PDSCH) reception", and "layer" is read as "(PDSCH) DMRS port". The configured grant settings and PUSCH setting information may be read as PDSCH setting information (PDSCH-Config information element). In addition, the DCI for scheduling PUSCH (DCI for UL) may be read as DCI format 0_0 / 0_1 / 0_2, etc., while the DCI for scheduling PDSCH may be read as DCI format 1_0 / 1_1 / 1_2, etc.

[0198] According to the third embodiment described above, MCS control can be appropriately implemented for each layer / DMRS port.

[0199] <Fourth Embodiment> The fourth embodiment relates to reporting on parameters for each layer (for example, a Channel State Information (CSI) report).

[0200] In NR, the UE measures the channel status using a reference signal (or a resource for that reference signal) and feeds back (reports) the CSI to the network (e.g., the base station).

[0201] The UE may measure the channel state using at least one of the following: Channel State Information Reference Signal (CSI-RS), Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block, Synchronization Signal (SS), or Demodulation Reference Signal (DMRS).

[0202] A CSI-RS resource may include at least one of the following: a Non Zero Power (NZP) CSI-RS resource, a Zero Power (ZP) CSI-RS resource, and a CSI Interference Measurement (CSI-IM) resource.

[0203] Resources for measuring signal components for CSI may be called Signal Measurement Resources (SMRs) or Channel Measurement Resources (CMRs). SMRs (CMRs) may include, for example, NZP CSI-RS resources for channel measurement, SSBs, etc.

[0204] Resources for measuring interference components for CSI may be called Interference Measurement Resources (IMRs). An IMR may include, for example, at least one of the following: an NZP CSI-RS resource, an SSB, a ZP CSI-RS resource, and a CSI-IM resource for interference measurement.

[0205] An SS / PBCH block is a block that includes synchronization signals (e.g., a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS)) and a PBCH (and its corresponding DMRS), and may also be called an SS block (SSB).

[0206] Furthermore, CSI may include at least one of the following: Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), SS / PBCH Block Resource Indicator (SSBRI), Layer Indicator (LI), Rank Indicator (RI), L1-RSRP (Layer 1 Reference Signal Received Power), L1-RSRQ (Reference Signal Received Quality), L1-SINR (Signal to Interference plus Noise Ratio), and L1-SNR (Signal to Noise Ratio).

[0207] The UE may report information regarding the appropriate power ratio for each layer (e.g., the preferred power ratio) to the network (e.g., the base station).

[0208] For example, a UE may include information indicating the power ratio between layers (e.g., Uplink Control Information (UCI)) in the CSI report and report it to the base station. The UCI, which indicates the (appropriate) power ratio between layers, may be called, for example, a Power Ratio Indicator (PRI). The PRI may be an index associated with the power ratio between layers.

[0209] The UE may transmit the CSI (UCI), including the PRI, using either PUCCH or PUSCH, or it may transmit it using PUSCH only.

[0210] Furthermore, both the appropriate power ratio and the CQI (described below) may be communicated using one parameter (a certain index) of the UCI. The correspondence between the value of this index and the power ratio and CQI (or MCS) may be specified / determined by upper-layer signaling, physical layer signaling, UE capability, or a combination thereof.

[0211] Alternatively, the appropriate MCS for each layer may be reported using a CSI report, either in place of or along with the appropriate power ratio.

[0212] The UE may report a CSI report to the base station that includes CQIs for each layer. This CSI report may include CQIs for multiple layers (multiple CQI indices), or it may include a CQI for one layer and a differential CQI for a CQI from that layer to a CQI for another layer. The differential CQI may have fewer bits than a regular CQI.

[0213] Figures 18A and 18B show an example of a CSI report including layer-specific CQIs in the fourth embodiment.

[0214] Figure 18A shows an example of a CSI report that a UE reports to a base station (BS) that includes the (normal) CQI index for Layer 1 and the (normal) CQI index for Layer 2.

[0215] Figure 18B shows an example of a CSI report that a UE reports to a base station (BS) that includes the (normal) CQI index for Layer 1 and a differential CQI index showing the difference from the Layer 1 CQI index for Layer 2.

[0216] When determining the CQI index of another layer based on the CQI index of one layer, the CQI index of the other layer may be calculated as: CQI index of one layer + CQI offset. The CQI offset may be interpreted interchangeably with the CQI index offset, differential CQI index, etc. The CQI offset may be an integer or a negative value.

[0217] The CQI index of one of the layers described above may represent the CQI index of the layer with the smallest index (e.g., Layer 1) or the layer with the largest index (e.g., the highest-ranked layer).

[0218] The CQI offset may be predetermined by specification, or it may be specified / determined by upper-layer signaling, physical layer signaling, UE capability, or a combination thereof. The number of bits in the CQI offset field included in the CSI report may be determined based on at least one of the following: the number of layers, upper-layer parameters, etc.

[0219] Figures 19A and 19B show an example of determining the MCS for multiple layers according to Embodiment 2.1. Figure 19A shows the correspondence between the CQI index and CQI parameters (modulation scheme, coding rate, spectral efficiency), which are also used in existing Rel.15 / 16 NR.

[0220] A table that shows such correspondences may also be called a CQI table or CQI index table.

[0221] Consider the case where the UE notifies CQI index = 7 in Figure 19A as the Layer 1 CQI index of the CSI report. Figure 19B shows an example of the correspondence between the levels of CQI offsets that can be notified by the differential CQI index included in the CSI report. The level may also mean how far the indicated CQI index is from the base CQI index. In this example, the differential CQI index in Figure 19B may indicate CQI indices = 6-9 in Figure 19A. In other words, in this example, the differential CQI index values ​​= 0, 1, 2, and 3 correspond to CQI indices = 7, 8, 9, and 6 in Figure 19A, respectively.

[0222] The correspondence between the differential CQI index value and the CQI offset (or indicated CQI index) may be specified / determined by upper-layer signaling, physical layer signaling, UE capability, or a combination thereof.

[0223] Reporting CQI values ​​for multiple layers using CQI index fields and differential CQI index fields is expected to require fewer bits (lower overhead) than reporting CQI values ​​for multiple layers using two CQI index fields.

[0224] The UE may report a CQI per PRI / layer to the network if at least one of the following conditions is met: • Reporting is configured using RRC parameters (for example, the RRC parameter "reportQuantity" in the CSI report settings (CSI-ReportConfig information element) specifies PRI reporting). • The receiving PDSCH is subjected to different MCS for each layer (for example, at least one of conditions 2-1 to 2-5, as reinterpreted with respect to the PDSCH in the third embodiment, is satisfied).

[0225] The bit width of PRI(CSI) may be determined (and may vary) based on the number of layers that require (are subject to reporting) for PRI / CQI.

[0226] [[CQI Table]] In Figure 19A above, a CQI table is shown in which one value of the CQI index (CQI field) corresponds to the CQI of one layer. However, a CQI table in which one value of the CQI index corresponds to the CQI of multiple layers may be used. In this case, the UE may determine the CQI of multiple layers from one CQI field, without relying on the CQI offset described above.

[0227] Furthermore, one CQI table showing CQIs for multiple layers may be referenced, or multiple CQI tables showing CQIs for separate layers may be referenced. For example, when a UE is scheduled to receive a 2-layer PDSCH / CSI-RS, it may determine the Layer 0 CQI based on the CQI field and a first table (a CQI table for Layer 0 CQI parameters), and then determine the Layer 1 CQI based on the same CQI field and a second table (a CQI table for Layer 1 CQI parameters).

[0228] The UE may determine which CQI table to reference based on the number of layers in the PDSCH / CSI-RS it receives.

[0229] Furthermore, when determining the CQI of one layer per CQI field, or when determining the CQI of multiple layers per CQI field, or both, the UE may determine the layer-specific CQI parameters by referring to the same (common) CQI table for each layer (for example, the cqi-table parameter in the CSI reporting settings (CSI-ReportConfig information element)), or it may determine the layer-specific CQI parameters by referring to different CQI tables for each layer.

[0230] The CQI table referenced for a given layer may be predetermined by the specification, or it may be specified / determined by upper-layer signaling, physical layer signaling, UE capability, or a combination thereof. For example, an RRC parameter may be set to specify the CQI table referenced for each layer.

[0231] According to the fourth embodiment described above, a CSI report containing information for each layer can be transmitted appropriately.

[0232] <Further modifications of the third embodiment> [MCS control per TRP in MTRP PDSCH] The layer-by-layer MCS control in the third embodiment may also be applied to the TRP-by-TRP MCS control in the PDSCH from MTRP (MTRP PDSCH).

[0233] In NR, it is being considered to use a single DCI to perform MTRP PDSCH iterations and instruct the UE to perform multiple (e.g., two) TCI states. Such operation may be called single-DCI (s-DCI) based Multi TRP operation.

[0234] Now, if sDCI specifies multiple RSs (for example, multiple RSs with multiple quasi-co-location (QCL) relationships, or multiple RSs with separate channels / signals and QCL type D) (in other words, specifying a TCI field that indicates multiple different TCI states), the UE may apply a different MCS for each PDSCH transmit (receive) corresponding to each specified RS.

[0235] For example, if the sDCI TCI code point detected by the UE indicates multiple TCI states (activated by MAC CE), the UE applies a different MCS to each PDSCH corresponding to each TCI state to perform the reception processing.

[0236] In the above-described third embodiment, this control may be implemented by an embodiment in which the "layer" is read as at least one of "TRP", "RS (例如, corresponding to the TCI state reference RS)", "PDSCH transmission / reception corresponding to RS", "PDSCH", "a group constituted by PDSCH transmission / reception corresponding to one or more RSs (a group including PDSCH transmission / reception corresponding to one or more RSs)", etc.

[0237] FIG. 20 is a diagram showing an example of MCS control for each PDSCH for MTRP PDSCH based on a further modification of the third embodiment. For example, assume a case where a sDCI that schedules MTRP PDSCH including a TCI field indicating TCI state 1 and TCI state 5 and information indicating the MCS for each PDSCH is notified to the UE from BS1.

[0238] In this case, as shown in FIG. 20, the UE may apply a low MCS index to the PDSCH (for BS1) corresponding to TCI state 1 and apply a high MCS index to the PDSCH (for BS2) corresponding to TCI state 5 and receive it.

[0239] <Others> Note that at least one of the above-described embodiments may be applied only to a UE that has reported a specific UE capability or supports the specific UE capability.

[0240] The specific UE capability may indicate at least one of the following: · Whether to support power control of PUSCH for each layer / port / TRP · Whether to support MCS control of PUSCH for each layer / port / TRP · Whether to support MCS control of PDSCH for each layer / port / TRP · Whether to support CSI (UCI) reporting for each layer / port / TRP.

[0241] Furthermore, the specific UE ability described above may be an ability for CB-based pushes, an ability for NCB-based pushes, or an ability that does not distinguish between the two.

[0242] Furthermore, the specific UE capability described above may be a capability that applies across all frequencies (commonly regardless of frequency), a capability that is frequency-specific (e.g., cell, band, BWP), a capability that is frequency-specific (e.g., FR1, FR2), or a capability that is subcarrier-specific.

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

[0244] Furthermore, at least one of the embodiments described above may be applied if the UE is configured by upper-layer signaling to provide specific information related to the embodiments described above (if not configured, the operation of, for example, Rel.15 / 16 will be applied). For example, such specific information may be information indicating the activation of power / MCS control for PUSCH / PDSCH per layer / port / TRP, or arbitrary RRC parameters for a particular release (e.g., Rel.18). The UE may also use upper-layer parameters to determine which of the embodiments / cases / conditions described above the basis for controlling the PHR.

[0245] The term "layer" in this disclosure may be interpreted as at least one of the following: "TRP", "RS (e.g., SRS, a reference RS corresponding to a TCI state)", "PUSCH transmission corresponding to an RS", "PDSCH transmission / reception corresponding to an RS", "PUSCH", "PDSCH", "a group consisting of one or more PUSCH transmissions corresponding to RS (a group including one or more PUSCH transmissions corresponding to RS)", or "a group consisting of one or more PDSCH transmissions / receptions corresponding to RS (a group including one or more PDSCH transmissions / receptions corresponding to RS)".

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

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

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

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

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

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

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

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

[0254] Furthermore, the user terminal 20 may communicate using at least one of the following methods at each CC: Time Division Duplex (TDD) and Frequency Division Duplex (FDD).

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

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

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

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

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

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

[0261] Also, in the wireless communication system 1, as uplink channels, a Physical Uplink Shared Channel (PUSCH) shared by each user terminal 20, a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), etc. may be used.

[0262] User data, upper layer control information, a System Information Block (SIB), etc. are transmitted by the PDSCH. User data, upper layer control information, etc. may be transmitted by the PUSCH. Also, a Master Information Block (MIB) may be transmitted by the PBCH.

[0263] 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 of at least one of the PDSCH and the PUSCH.

[0264] Note that the DCI for scheduling the PDSCH may be called a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be called a UL grant, a UL DCI, etc. Note that the PDSCH may be read as DL data, and the PUSCH may be read as UL data.

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

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

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

[0268] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted when describing various channels.

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

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

[0271] Furthermore, in the wireless communication system 1, the Uplink Reference Signal (UL-RS) may transmit the Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), etc. The DMRS may also be called the User-Specific Reference Signal (UE-specific Reference Signal).

[0272] (base station) Figure 22 shows an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, transceiver unit 120, transceiver antenna 130, and transmission line interface 140 may be provided.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0287] The transmission path interface 140 may send and receive signals (backhaul signaling) with 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.

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

[0289] The transmitting / receiving unit 120 may also transmit information (for example, DCI and RRC parameters) to the user terminal 20 for applying different modulation and coding schemes (MCS) to multiple layers.

[0290] The transmitting / receiving unit 120 may receive the multi-layer uplink sharing channels (PUSCH) transmitted by the user terminal 20 with the different MCS applied based on the information.

[0291] Furthermore, the transmitting / receiving unit 120 may transmit information (e.g., DCI, RRC parameters) to the user terminal 20 for determining different modulation and coding schemes (MCS) for multiple layers.

[0292] The control unit 110 may perform control to transmit the downlink shared channel (PDSCH) of the multiple layers by applying the different MCSs.

[0293] Furthermore, the transmitting / receiving unit 120 may transmit information (e.g., DCI, RRC parameters) for applying different power ratios to multiple layers to the user terminal 20.

[0294] The transmitting / receiving unit 120 may receive the multi-layer uplink sharing channel (PUSCH) transmitted by the user terminal 20 with the different power ratios applied based on the information.

[0295] Furthermore, the transmitting / receiving unit 120 may send information (for example, DCI, RRC parameters) to the user terminal 20 instructing it to generate a Channel State Information (CSI) report that includes information for each layer.

[0296] The transmitting / receiving unit 120 may receive the CSI report from the user terminal 20.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0313] In this disclosure, the transmitting and receiving units of the user terminal 20 may consist of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.

[0314] The control unit 210 may also perform control to apply different modulation and coding schemes (MCS) to multiple layers. The transmitting / receiving unit 220 may apply the different MCSs to transmit the uplink shared channels (PUSCH) of the multiple layers.

[0315] The control unit 210 may determine the different MCSs based on two MCS fields included in the downlink control information (DCI).

[0316] The control unit 210 may determine the different MCS based on one MCS field included in the downlink control information.

[0317] Furthermore, the control unit 210 may perform control to determine different modulation and coding schemes (MCS) for multiple layers. The transmitting / receiving unit 220 may apply the different MCSs to receive the downlink shared channels (PDSCH) of the multiple layers.

[0318] The control unit 210 may determine the different MCSs based on two MCS fields included in the downlink control information (DCI).

[0319] The control unit 210 may determine the different MCS based on one MCS field included in the downlink control information.

[0320] Furthermore, the control unit 210 may perform control to apply different power ratios to multiple layers. The transmitting / receiving unit 220 may apply the different power ratios to transmit on the uplink shared channel (PDSCH) of the multiple layers.

[0321] The control unit 210 may determine the different power ratios based on the precoding information and layer number field included in the downlink control information.

[0322] The control unit 210 may determine the different power ratios based on a Transmitted Precoding Matrix Indicator (TPMI) indicated by downlink control information.

[0323] Furthermore, the control unit 210 may generate (derive) a Channel State Information (CSI) report that includes information for each layer. The transmitting / receiving unit 220 may transmit the CSI report.

[0324] The control unit 210 may generate the CSI report, which includes information regarding the appropriate power ratio for each layer.

[0325] The control unit 210 may generate the CSI report, which includes Channel Quality Indicator (CQI) indices for each layer.

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

[0327] Here, functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission may be called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

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

[0329] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

[0330] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, processing may be performed by one processor, or by two or more processors simultaneously, sequentially, or by other means. Note that processor 1001 may be implemented using one or more chips.

[0331] 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 the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication via the communication device 1004, or to control at least one of the reading and writing of data in the memory 1002 and storage 1003.

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

[0333] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly.

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

[0335] Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disk (Compact Disc ROM (CD-ROM)), a digital multipurpose disk, a Blu-ray 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 called an auxiliary storage device.

[0336] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitting / receiving unit 120 (220), transmitting / receiving antenna 130 (230), etc., may be implemented by the communication device 1004. The transmitting / receiving unit 120 (220) may be implemented with physically or logically separated implementations of a transmitting unit 120a (220a) and a receiving unit 120b (220b).

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

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

[0339] 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), and a field programmable gate array (FPGA), and some or all of each functional block may be implemented using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0340] (modified version) In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.

[0341] A wireless frame may consist of one or more periods (frames) in the time domain. Each of these periods (frames) constituting a wireless frame may be called a subframe. Furthermore, a subframe may consist 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.

[0342] Here, the neuralelogy may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The neuralelogy may be, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, or specific windowing processes performed by the transceiver in the time domain.

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

[0344] A slot may include multiple mini-slots. Each mini-slot may consist of one or more symbols in the time domain. Mini-slots may also be called sub-slots. Mini-slots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called a PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called a PDSCH (PUSCH) mapping type B.

[0345] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable.

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

[0347] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0348] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0349] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0350] A TTI with a time length of 1 ms may also be called a normal TTI (TTI in 3GPP Rel.8-12), a long TTI, a normal subframe, a long subframe, or a slot. A TTI shorter than a normal TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, or a slot.

[0351] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0352] A Resource Block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0353] Furthermore, an RB may contain one or more symbols in the time domain and may have the length of one slot, one minislot, one subframe, or one TTI. Each TTI, subframe, etc., may consist of one or more resource blocks.

[0354] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

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

[0356] A Bandwidth Part (BWP) (also called a partial bandwidth) may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a BWP.

[0357] A BWP may include UL BWPs (BWPs for UL) and DL BWPs (BWPs for DL). One or more BWPs may be configured within a single carrier for a UE.

[0358] At least one of the configured BWPs may be active, and the UE does not need to assume that it will transmit or receive a given channel / signal outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0359] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative examples. For instance, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots within a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

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

[0361] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements that use these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0362] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. 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 voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0363] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.

[0364] Input and output information and signals may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information and signals may be overwritten, updated, or appended to. Output information and signals may be deleted. Input information and signals may be transmitted to other devices.

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

[0366] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Element (CE).

[0367] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not providing notification of the specified information or by providing notification of other information).

[0368] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value represented as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).

[0369] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

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

[0371] The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations).

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

[0373] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "panel", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0374] A base station can house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

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

[0376] A mobile station may also be called a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term.

[0377] 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 body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile 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 be 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.

[0378] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this 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)). In this case, the user terminal 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

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

[0380] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes with 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 (for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), etc., but not limited to these), or a combination thereof.

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

[0382] Each aspect / embodiment described in this disclosure includes Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or 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®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), and IEEE This may be applied to systems utilizing 802.20, Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, as well as next-generation systems that extend these. It may also be applied in combination with multiple systems (for example, a combination of LTE or LTE-A and 5G).

[0383] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

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

[0385] The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to include judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in tables, databases, or other data structures), ascertaining, etc.

[0386] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).

[0387] Furthermore, "judgment (decision)" can be considered as "judging (deciding)" something like resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" can be considered as "judging (deciding)" something about an action.

[0388] Furthermore, "judgment (decision)" can be replaced with "assuming," "expecting," or "considering."

[0389] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

[0390] In this disclosure, when two elements are connected, they can be considered to be “connected” or “coupled” to each other using one or more wires, cables, printed electrical connections, etc., and, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, or optical domain (both visible and invisible).

[0391] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0392] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

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

[0394] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The invention described herein can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined in the claims. Therefore, the descriptions herein are for illustrative purposes only and do not imply any limitation on the invention described herein.

Claims

1. A receiving unit that receives parameters for determining a first transmit power value corresponding to a first panel for Multi Input Multi Output (MIMO), A control unit that determines a second transmit power value corresponding to a second panel for MIMO based on the first transmit power value, A terminal having a transmitting unit that performs transmission on the uplink sharing channel of the first panel by applying the first transmission power value, and performs transmission on the uplink sharing channel of the second panel by applying the second transmission power value.

2. The terminal according to claim 1, wherein the second transmission power value is different from the first transmission power value.

3. The terminal according to claim 1, wherein when the control unit receives a Medium Access Control element indicating activation with respect to power control of the uplink sharing channel for each panel, it determines the second transmit power value based on the first transmit power value.

4. A step of receiving parameters for setting a first transmit power value corresponding to a first panel for Multi Input Multi Output (MIMO), The steps include: performing control to determine a second transmit power value corresponding to a second panel for MIMO based on the first transmit power value; A wireless communication method for a terminal, comprising the steps of: applying the first transmit power value to transmit on the uplink sharing channel of the first panel; and applying the second transmit power value to transmit on the uplink sharing channel of the second panel.

5. A transmitting unit that transmits parameters to a terminal for setting a first transmit power value corresponding to a first panel for Multi Input Multi Output (MIMO), A base station having a receiving unit that receives an uplink sharing channel of a first panel transmitted by the terminal applying the first transmit power value based on the parameters, and an uplink sharing channel of a second panel for MIMO transmitted by applying a second transmit power value determined by the terminal based on the first transmit power value.

6. A system comprising a terminal according to any one of claims 1 to 3 and a base station according to claim 5.