Terminal, radio communication method, and base station

Abstract

To appropriately control UL transmission using three antenna ports.SOLUTION: A terminal according to an aspect of the present disclosure has: a receiving section that receives an upper layer parameter for noncodebook-based 3-antenna-port (3TX) uplink (UL) transmission; and a control section that controls validation of the noncodebook-based 3TX UL transmission on the basis of the upper layer parameter.SELECTED DRAWING: Figure 14

Description

[Technical Field]

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

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

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

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

[0005] Rel.15 NR supports uplink (UL) multi-input multi-output (MIMO) transmission with up to four layers. For future NR, support for UL transmission with more than four layers is being considered to achieve higher spectral efficiency. For example, for Rel.18 NR, maximum 6-rank transmission using six antenna ports and maximum 6- or 8-rank transmission using eight antenna ports are being considered.

[0006] On the other hand, there may be cases where uplink full power transmission is not supported in Rel. 19 and later. In such cases, to easily realize codebook-based transmission using three antenna ports (also called 3TX), it is being considered to specify a noncoherent UL codebook (a noncoherent codebook for UL).

[0007] Non-codebook-based UL transmission for 3TX is also being investigated.

[0008] However, the provisions regarding non-codebook-based UL transmission for 3TX are not sufficiently clear.

[0009] Therefore, one object of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately control UL transmission using, for example, three antenna ports. [Means for solving the problem]

[0010] A terminal according to one embodiment of the present disclosure includes a receiving unit that receives upper layer parameters for non-codebook-based uplink (UL) transmission using three antenna ports (3TX), and a control unit that controls enabling of the non-codebook-based 3TX UL transmission based on the upper layer parameters. [Effects of the Invention]

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

[0012] [Figure 1] FIG. 1 is a diagram illustrating an example of a table of a precoding matrix W for single-layer (rank-1) transmission using four antenna ports when a transform precoder is disabled in Rel. 16 NR. [Figure 2] FIG. 2 is a diagram illustrating an example of a table of a precoding matrix W for two-layer (rank-2) transmission using four antenna ports when the transform precoder is disabled in Rel. 16 NR. [Figure 3] FIG. 3 is a diagram illustrating an example of a table of a precoding matrix W for three-layer (rank 3) transmission using four antenna ports when the transform precoder is disabled in Rel. 16 NR. [Figure 4] FIG. 4 is a diagram illustrating an example of a table of a precoding matrix W for four-layer (rank 4) transmission using four antenna ports when the transform precoder is disabled in Rel. 16 NR. [Figure 5] Fig. 5A is a diagram showing an example of a table of precoding matrices W for single-layer (rank-1) transmission using two antenna ports in Rel.16 NR. Fig. 5B is a diagram showing an example of a table of precoding matrices W for two-layer (rank-2) transmission using two antenna ports in Rel.16 NR when transform precoding is disabled. [Figure 6]FIG. 6 is a diagram showing an example of the correspondence between the field values ​​of the precoding information and the number of layers, and the number of layers and TPMI in Rel. 16 NR. [Figure 7] 7A to 7C are diagrams illustrating an SRI indication or a second SRI indication when transmitting a codebook-based PUSCH in Rel. 17. [Figure 8] FIG. 8 is a diagram illustrating an example of an antenna layout for eight antenna ports. [Figure 9] FIG. 9 is a diagram showing candidates for precoding matrix W for each transmission rank using three antenna ports. [Figure 10] 10A to 10C are diagrams showing examples of tables (separate tables) of precoding matrices W for layer 1 to 3 (rank 1 to 3) transmission using three antenna ports when the transform precoder is disabled. [Figure 11] FIG. 11 is a diagram showing an example of a table (joint table) of precoding matrices W for layer 1 to 3 (rank 1 to 3) transmission using three antenna ports when the transform precoder is disabled. [Figure 12] 12A and 12B are diagrams showing an example of the correspondence between the field values ​​of the precoding information and the number of layers, and the number of layers and TPMI. [Figure 13] FIG. 13 is a diagram showing an example of the correspondence between the field values ​​of the precoding information and the number of layers, and the number of layers and TPMI. [Figure 14] 14A to 14C are diagrams illustrating an example of a correspondence relationship between a PTRS and a DMRS in non-codebook-based 3TX UL transmission of the present disclosure. [Figure 15] 15A to 15C are diagrams illustrating an example of a correspondence relationship between a PTRS and a DMRS in codebook-based 3TX UL transmission of the present disclosure. [Figure 16] 16A to 16C are diagrams illustrating an example of a correspondence relationship between PTRS and DMRS in 3TX UL transmission of the present disclosure. [Figure 17]FIG. 17 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 18] FIG. 18 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 19] FIG. 19 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 20] FIG. 20 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. [Figure 21] FIG. 21 is a diagram illustrating an example of a vehicle according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0013] (SRS, PUSCH transmission control) In Rel.15 NR, a terminal (user terminal, User Equipment (UE)) may receive information (SRS configuration information, for example, parameters in the RRC control element "SRS-Config") used to transmit a measurement reference signal (for example, a Sounding Reference Signal (SRS)).

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

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

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

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

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

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

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

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

[0022] The spatial relationship information of the SRS may include at least one of an SSB index, a CSI-RS resource ID, and an SRS resource ID as an index of the predetermined reference signal.

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

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

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

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

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

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

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

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

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

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

[0033] The UE may be configured to use codebook-based PUSCH transmission or non-codebook-based PUSCH transmission by a higher layer parameter "txConfig" indicating a transmission scheme. The parameter may indicate a value of "codebook" or "non-codebook."

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

[0035] (Determining PUSCH Precoder in Codebook (CB)-Based Transmission) As mentioned above, the UE may determine the precoder for PUSCH transmission based on the SRI, TRI, TPMI, etc. in the case of codebook (CB) based transmission.

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

[0037] The TRI and TPMI may be specified by a "Precoding information and number of layers" field of the DCI, which is also referred to as the "Precoding information field" for simplicity.

[0038] The UE may report UE capability information related to a precoder type, and the base station may configure the precoder type based on the UE capability information through higher layer signaling. The UE capability information may be information on the precoder type used by the UE in PUSCH transmission (for example, may be represented by an RRC parameter "pusch-TransCoherence").

[0039] The UE may determine the precoder to be used for PUSCH transmission based on precoder type information (e.g., RRC parameter "codebookSubset") included in PUSCH configuration information notified by higher layer signaling (e.g., "PUSCH-Config" information element of RRC signaling). The UE may be configured with a subset of the PMI specified by the TPMI by the codebookSubset.

[0040] The precoder type may be specified by any one of full coherent, partial coherent, and non-coherent, or a combination of at least two of these (for example, it may be expressed by parameters such as "fully and partial and non-coherent" or "partial and non-coherent").

[0041] For example, the RRC parameter "pusch-TransCoherence" indicating UE capabilities may indicate full coherence, partial coherence, or noncoherence, and the RRC parameter "codebookSubset" may indicate full and partial and noncoherence, partial and noncoherence, or noncoherence.

[0042] Fully coherent may mean that all antenna ports used for transmission are synchronized (may also be expressed as being able to match the phase, being able to control the phase for each coherent antenna port, being able to apply a precoder appropriately for each coherent antenna port, etc.). Partially coherent may mean that some of the antenna ports used for transmission are synchronized, but those some ports cannot be synchronized with other ports. Non-coherent may mean that each antenna port used for transmission cannot be synchronized.

[0043] Note that a UE that supports a fully coherent precoder type may be assumed to support partially coherent and non-coherent precoder types, and a UE that supports a partially coherent precoder type may be assumed to support a non-coherent precoder type.

[0044] In the present disclosure, the terms precoder type, coherency, PUSCH transmission coherence, coherent type, coherence type, codebook type, codebook subset, codebook subset type, etc. may be read interchangeably.

[0045] The UE may determine, from multiple precoders (which may also be called precoding matrices, codebooks, etc.) for CB-based transmission, a precoding matrix corresponding to a TPMI index obtained from the DCI (e.g., DCI format 0_1, etc.) that schedules the UL transmission.

[0046] Figure 1 shows an example of the association between codebook subsets and TPMI indices. Figure 1 corresponds to a table of precoding matrices W for single-layer (rank-1) transmission using four antenna ports when transform precoding (also called a transform precoder) is disabled in Rel. 16 NR. Figure 1 shows the corresponding Ws in ascending order of TPMI indices from left to right (similarly in Figure 2).

[0047] The correspondence relationship (which may be called a table) showing the TPMI index and the corresponding W as shown in Fig. 1 is also called a codebook. A part of this codebook is also called a codebook subset.

[0048] In FIG. 1, if the codebook subset (codebookSubset) is fully, partial, and non-coherent (fullyAndPartialAndNonCoherent), the UE is notified of a TPMI (TPMI index) of one of 0 to 27 for single layer transmission. Also, if the codebook subset is partial and non-coherent (partialAndNonCoherent), the UE is configured with a TPMI of one of 0 to 11 for single layer transmission. If the codebook subset is non-coherent, the UE is configured with a TPMI of one of 0 to 3 for single layer transmission.

[0049] In Figure 1, when a TPMI from 0 to 3 is notified, a non-coherent precoder is applied. When a TPMI from 4 to 11 is notified, a partially coherent precoder is applied. When a TPMI from 12 to 27 is notified, a fully coherent precoder is applied.

[0050] 2 to 4 correspond to tables of precoding matrices W for 2-4 layer (rank 2-4) transmission using four antenna ports in the case where transform precoding is disabled in Rel. 16 NR.

[0051] According to Figure 2, the TPMI that the UE is informed of for two-layer transmission is from 0 to 21 (codebook subset full, partial and non-coherent), from 0 to 13 (codebook subset partial and non-coherent), or from 0 to 5 (codebook subset non-coherent).

[0052] According to Figure 3, the TPMI that the UE is informed of for three-layer transmission is 0 to 6 (codebook subset full, partial and non-coherent), 0 to 2 (codebook subset partial and non-coherent) or 0 (codebook subset non-coherent).

[0053] According to Figure 4, the TPMI that the UE is informed of for 4-layer transmission is 0 to 4 (codebook subset is full, partial and non-coherent), 0 to 2 (codebook subset is partial and non-coherent) or 0 (codebook subset is non-coherent).

[0054] Figure 5A corresponds to a table of precoding matrix W for single-layer (rank-1) transmission using two antenna ports in Rel.16 NR. Figure 5B corresponds to a table of precoding matrix W for two-layer (rank-2) transmission using two antenna ports in Rel.16 NR when transform precoding is disabled.

[0055] According to Figure 5A, the TPMI signaled to the UE for two-port single layer transmission is between 0 and 5 (codebook subsets are full, partial and non-coherent) or between 0 and 1 (codebook subset is non-coherent). If the signaled TPMI is between 0 and 1, a non-coherent precoder is applied. If the signaled TPMI is between 2 and 5, a fully coherent precoder is applied.

[0056] According to FIG. 5B, the TPMI that the UE is informed of for two-port two-layer transmission is between 0 and 2 (codebook subsets are complete, partial and non-coherent) or 0 (codebook subset is non-coherent).

[0057] Note that a precoding matrix in which only one element per column is non-zero may be called a non-coherent codebook. A precoding matrix in which a certain number of elements per column (greater than one, but not all elements in the column) are non-zero may be called a partially coherent codebook. A precoding matrix in which all elements per column are non-zero may be called a fully coherent codebook.

[0058] The non-coherent codebook and the partially coherent codebook may be referred to as an antenna selection precoder, an antenna port selection precoder, etc. For example, the non-coherent codebook (non-coherent precoder) may be referred to as a 1-port selection precoder, a 1-port port selection precoder, etc. Furthermore, the partially coherent codebook (partially coherent precoder) may be referred to as an x-port (x is an integer greater than 1) selection precoder, an x-port port selection precoder, etc. The fully coherent codebook may be referred to as a non-antenna selection precoder, a full-port precoder, etc. In the present disclosure, the terms codebook, codebook subset, and precoder may be interchangeable.

[0059] In the present disclosure, a partially coherent codebook may correspond to a codebook (precoding matrix) corresponding to a TPMI specified by DCI for codebook-based transmission by a UE configured with a partially coherent codebook subset (e.g., RRC parameter "codebookSubset"="partialAndNonCoherent"), excluding a codebook corresponding to a TPMI specified by a UE configured with a non-coherent codebook subset (e.g., RRC parameter "codebookSubset"="nonCoherent") (i.e., in the case of single-layer transmission with four antenna ports, codebooks with TPMI=4 to 11).

[0060] In the present disclosure, a fully coherent codebook may refer to a codebook (precoding matrix) corresponding to a TPMI specified by DCI for codebook-based transmission by a UE configured with a fully coherent codebook subset (e.g., RRC parameter "codebookSubset"="fullyAndPartialAndNonCoherent"), excluding a codebook corresponding to a TPMI specified by a UE configured with a partially coherent codebook subset (e.g., RRC parameter "codebookSubset"="partialAndNonCoherent") (i.e., in the case of single-layer transmission with four antenna ports, codebooks with TPMI=12 to 27).

[0061] As can be seen from FIGS. 5A and 5B, there is no partially coherent precoder for two-antenna port transmission, and therefore the setting in which the codebook subset is partial and non-coherent does not need to be applied to two-antenna ports.

[0062] (Precoding Information Field) As described above, the UE may determine the TPMI and the number of layers (transmission rank) for a PUSCH based on the precoding information field of the DCI (eg, DCI format 0_1 / 0_2) that schedules the PUSCH.

[0063] For a codebook-based PUSCH, the number of bits of the precoding information field may be determined (or may vary) based on a setting for enabling or disabling a transform precoder for the PUSCH (e.g., upper layer parameter transformPrecoder), a setting for a codebook subset for the PUSCH (e.g., upper layer parameter codebookSubset), a setting for the maximum number of layers for the PUSCH (e.g., upper layer parameter maxRank), a setting for uplink full power transmission for the PUSCH (e.g., upper layer parameter ul-FullPowerTransmission), the number of antenna ports for the PUSCH, etc.

[0064] 6 is a diagram showing an example of a correspondence relationship between the field values ​​of precoding information and the number of layers and the number of layers and TPMI in Rel.16 NR. The correspondence relationship in this example is a correspondence relationship for four antenna ports when the transform precoder is disabled, the maximum rank (maxRank) is set to 2, 3, or 4, and uplink full power transmission is not set, is set to full power mode 2 (fullpowerMode2), or is set to full power, but is not limited to this. Note that it will be obvious to those skilled in the art that the illustrated "bit field mapped to index" indicates the field values ​​of the precoding information and the number of layers.

[0065] In FIG. 6, the precoding information field is 6 bits when a fully coherent (fullyAndPartialAndNonCoherent) codebook subset is configured in the UE, 5 bits when a partially coherent (partialAndNonCoherent) codebook subset is configured, and 4 bits when a noncoherent (nonCoherent) codebook subset is configured.

[0066] As shown in Figure 6, the number of layers and TPMI corresponding to a certain precoding information field value may be the same (common) regardless of the codebook subset configured in the UE. For example, in Figure 6, the number of layers and TPMI indicated by values ​​= 0-11 in the precoding information field may be the same for the fully coherent (fullyAndPartialAndNonCoherent), partial coherent (partialAndNonCoherent), and noncoherent codebook subsets. Also, in Figure 6, the number of layers and TPMI indicated by values ​​= 0-31 in the precoding information field may be the same for the fully coherent (fullyAndPartialAndNonCoherent) and partial coherent (partialAndNonCoherent) codebook subsets.

[0067] The precoding information field may be 0 bits for a non-codebook-based PUSCH, and may be 0 bits for a codebook-based PUSCH with one antenna port.

[0068] (SRS setting for codebook-based PUSCH) FIG. 7A shows the case in Rel. 17 where ul-FullPowerTransmission is not set, or ul-FullPowerTransmission=fullpowerMode1, or ul-FullPowerTransmission=fullpowerMode2, or ul-FullPowerTransmission=fullpower and N SRS 7B is a diagram illustrating an SRI indication or a second SRI indication when transmitting a codebook-based PUSCH in the case of ul-FullPowerTransmission=fullpowerMode2 and N SRS7C is a diagram showing the SRI indication or the second SRI indication for codebook-based PUSCH transmission when ul-FullPowerTransmission=fullpowerMode2 and N SRS 10 shows an SRI indication or a second SRI indication for codebook-based PUSCH transmission when SRI=4.

[0069] The SRI indication corresponds to the SRS resource indicator field of the DCI, and the second SRI indication corresponds to the Second SRS resource indicator field of the DCI. The SRS resource set indicator field is 2 bits when txConfig=nonCodeBook and there are two SRS resource sets configured by srs-ResourceSetToAddModList associated with the "nonCodeBook" usage, or when txConfig=codebook and there are two SRS resource sets configured by srs-ResourceSetToAddModList associated with the "codebook" usage. Otherwise, the SRS resource set indicator field is 0 bit.

[0070] When the upper layer parameter txConfig=codebook is set, the SRS resource indicator field is set to [log2(N SRS )] bits. SRS is the number of configured SRS resources in the SRS resource set indicated by the SRS resource set indicator field (if present); otherwise, N SRS is the number of configured SRS resources associated with the upper layer parameter usage of value 'codeBook' within the SRS resource set configured by the upper layer parameter srs-ResourceSetToAddModList.

[0071] In codebook-based transmission, the PUSCH is scheduled by DCI format 0_0, DCI format 0_1, DCI format 0_2, or semi-statically configured. Only one or two SRS resource sets can be configured in SRS-ResourceSetToAddModList with the higher layer parameter use "codebook" of SRS-ResourceSet. Also, only one or two SRS resource sets can be configured in srs-ResourceSetToAddModListDCI-0-2 with the higher layer parameter use "codebook" of SRS-ResourceSet.

[0072] When two SRS resource sets are configured by setting the use of the upper layer parameters of SRS-ResourceSet to "codebook" in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, one or two SRIs and one or two TPMIs are given by two SRS resource indication fields and two precoding information fields, respectively.

[0073] The UE applies the indicated SRI(s) and TPMI(s) to one or more PUSCH repetitions according to the associated SRS resource sets of the PUSCH repetitions. If two SRS resource sets are configured in SRS-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 and the usage of the higher layer parameters of SRS-ResourceSet is set to "codebook", the UE does not expect different numbers of SRS resources to be configured in the two SRS resource sets.

[0074] For codebook-based transmission, only one SRS resource from the SRS resource set may be indicated based on the SRI. The maximum number of configured SRS resources for codebook-based transmission is 2, except when the upper layer parameter "ul-FullPowerTransmission" is set to "fullpowerMode2". If aperiodic SRS is configured for the UE, the SRS request field in the DCI triggers the transmission of the aperiodic SRS resource.

[0075] Unless the higher layer parameter "ul-FullPowerTransmission" is set to "fullpowerMode2", if multiple SRS resources are configured to "codebook" by an SRS-ResourceSet, the UE expects the higher layer parameter "nrofSRS-Port" of the SRS-Resource in the SRS-ResourceSet to be set to the same value for all these SRS resources.

[0076] When the upper layer parameter "ul-FullPowerTransmission" is set to "fullpowerMode2", the following (1) to (3) apply. (1) Within an SRS resource set whose usage is set to “codebook”, the UE can configure one SRS resource or multiple SRS resources with the same or different number of SRS ports. (2) When multiple SRS resources are configured in an SRS resource set, up to two different spatial relationships can be configured for all SRS resources in the SRS resource set whose usage is set to “codebook.” (3) Depending on the UE capabilities, up to two or four SRS resources are supported in an SRS resource set with usage set to “codebook.”

[0077] In the case of a normal codebook-based PUSCH, one SRS resource set having two SRS resources with the same number of ports can be configured. In the case of codebook-based PUSCH repetition (for multiple transmission / reception points (TRPs)), two SRS resource sets each having the same number of SRS resources can be configured. In the case of "fullpowerMode2" in the codebook base, one SRS resource set, SRS resources with the same number of ports or different numbers of ports can be configured.

[0078] (Transmitting on more than 4 antenna ports) Rel.15 / 16 NR supports uplink (UL) multi-input multi-output (MIMO) transmission with up to four layers. To achieve higher spectral efficiency for future wireless communication systems, support for UL transmission with more than four layers is being considered. For example, for Rel.18 NR, maximum 6-rank transmission using six antenna ports and maximum 6- or 8-rank transmission using eight antenna ports are being considered.

[0079] FIG. 8 is a diagram showing an example of an antenna layout with eight antenna ports. Ng is the number of antenna groups. M is the number of antennas (or antenna elements) in the first dimension, and N is the number of antennas (or antenna elements) in the second dimension. The first and second dimensions are, for example, the horizontal and vertical directions. P is the number of polarization planes. When P=2, it becomes a cross-polarized antenna.

[0080] An antenna group may be referred to as a coherent group. A coherent group may include one or more coherent ports. For example, a partially coherent UE may have multiple coherent groups. Antenna ports within a coherent group may be coherent. Antenna ports between different coherent groups may not be coherent.

[0081] Each coherent group may correspond to a different transmit panel / transmit chain / SRS resource set / RS resource set / spatial relation information / joint Transmission Configuration Indication state (joint TCI state) / UL TCI state / received TRP. Here, the SRS resource set may specifically correspond to an SRS resource set used for codebook or non-codebook. Also, each coherent group may correspond to a different received TRP. Also, the coherent group may be called a coherent antenna group, a port group, an antenna set, etc.

[0082] The UE may report supported antenna groups, antenna configuration information, and the number of coherent antennas as UE capability information. The UE may also be configured with coherent groups (e.g., the number of coherent groups and the number of ports included in each coherent group) via higher layer signaling.

[0083] Note that the antenna layout is not limited to the example shown in Figure 8. For example, the number of panels on which antennas are arranged, the orientation of the panels, the coherency of each panel / antenna (fully coherent, partially coherent, non-coherent, etc.), the antenna arrangement in a specific direction (horizontal, vertical, etc.), and the polarization antenna configuration (single polarization, cross polarization, number of polarization planes, etc.) may differ from the examples in Figures 7A and 7B. dG-H and dG-V represent the horizontal and vertical spacing between the centers of adjacent antenna groups, respectively.

[0084] Furthermore, while Rel. 15 / 16 NR supported the transmission of one codeword (CW) in one PUSCH, for Rel. 18 NR, UEs are being considered to transmit more than one CW in one PUSCH. For example, support for two CW transmissions for ranks 5-8 and two CW transmissions for ranks 2-8 are being considered.

[0085] In addition, in Rel.15 and Rel.16 UEs, it is assumed that only one beam / panel is used for UL transmission at a given time, but in Rel.17 and later, simultaneous UL transmission (e.g., PUSCH transmission) of multiple beams / multiple panels for one or more TRPs is being considered to improve UL throughput and reliability. Note that simultaneous PUSCH transmission of multiple beams / multiple panels may correspond to PUSCH transmission with a number of layers greater than four, or may correspond to PUSCH transmission with a number of layers less than or equal to four.

[0086] Also, precoding matrices for UL transmission using more than four antenna ports (a number of antenna ports greater than four) are being considered. For example, a codebook for 8-port transmission (which may be called an 8 TX UL codebook, etc.) is being considered.

[0087] (Codebook-based transmission using three antenna ports) However, in Rel. 19 and later, there may be cases where the above-mentioned uplink (UL) full power transmission is not supported and SRS enhancement / extension is not performed. In such cases, the specification of a non-coherent UL codebook (a non-coherent codebook for UL) is being considered to easily realize 3-antenna-port codebook-based transmission.

[0088] <Codebook for 3TX UE> A codebook for a UE that supports layer 1 to 3 transmission using three antenna ports may be referred to as a non-coherent UL codebook using three antenna ports.

[0089] Fig. 9 is a diagram showing candidates for precoding matrix W for each transmission rank using three antenna ports. Figs. 10A to 10C are diagrams showing an example of a table (separate table) of precoding matrix W for transmission of layers 1 to 3 (ranks 1 to 3) using three antenna ports when the transform precoder is disabled. Fig. 11 is a diagram showing an example of a table (joint table) of precoding matrix W for transmission of layers 1 to 3 (ranks 1 to 3) using three antenna ports when the transform precoder is disabled. In Figs. 10 and 11, the TPMI index in the W column increases from left to right (for example, from 0 to 2). The same applies below.

[0090] The non-coherent UL codebook for 3TX UE may be defined as shown in FIGS.

[0091] The precoding matrices W for rank 1 (single layer), rank 2 (two layers), and rank 3 (three layers) may be defined by separate tables (separate tables shown in Figures 10A to 10C) or by one (single) table (joint table shown in Figure 11).

[0092] As shown in Figure 9, the precoding matrix W for rank 1 (single layer) may include three precoders. As shown in Figures 9 and 10A, in a separate table, the three precoders may correspond to TPMI indices 0 to 2. As shown in Figures 9 and 11, in a single table, the three precoders may correspond to TPMI indices 0 to 2.

[0093] As shown in Figure 9, the precoding matrix W for rank 2 may include three precoders. As shown in Figures 9 and 10B, in a separate table, the three precoders may correspond to TPMI indices 0 to 2. As shown in Figures 9 and 11, in a single table, the three precoders may correspond to TPMI indices 3 to 5.

[0094] As shown in Figure 9, the precoding matrix W for rank 3 may include one precoder. As shown in Figures 9 and 10C, in a separate table, one precoder may correspond to TPMI index 0. As shown in Figures 9 and 11, in a single table, one precoder may correspond to TPMI index 6.

[0095] Also, the maximum rank number (1 to 3) supported by the UE (3TX UE) may be reported in the UE capabilities.

[0096] <Bit field for codebook for 3TX UE> 12A and 12B are diagrams showing an example of the correspondence between the field values ​​of the precoding information and the number of layers, and the number of layers and TPMI. Fig. 12A corresponds to the separate table described in Fig. 10, and Fig. 12B corresponds to the single table described in Fig. 11.

[0097] The UE may be configured / instructed to use a codebook (codebook subset) for 3TX UEs. For example, the UE may determine the precoder (TPMI and number of layers) to be applied based on the bit fields shown in Figure 12. The bit fields shown in Figure 12 may be included in DCI (e.g., DCI format 0_1 / 0_2) that schedules the PUSCH.

[0098] 12A, when the codebook subset is non-coherent and the maximum rank number (transmission rank) is 1, bit field indexes (bit fields mapped to indexes) 0 to 2 correspond to (indicate) TPMI=0 to 2 in one layer, respectively. Bit field index 3 may be a reserved bit.

[0099] Also, if the codebook subsets are non-coherent and the maximum rank number is 2, bit field indices 0 to 2 correspond to (indicate) TPMI=0 to 2 in layer 1, respectively, and bit field indices 3 to 5 correspond to TPMI=0 to 2 in layer 2, respectively. Bit field indices 6 and 7 may be reserved bits.

[0100] Also, if the codebook subsets are non-coherent and the maximum rank number is 3, bit field indexes 0 to 2 correspond to (indicate) TPMI=0 to 2, respectively, in layer 1, bit field indexes 3 to 5 correspond to TPMI=0 to 2, respectively, in layer 2, and bit field index 6 corresponds to TPMI=0 in layer 3. Bit field index 7 may be a reserved bit.

[0101] 12B, when the codebook subset is non-coherent and the maximum rank number (transmission rank) is 1, bit field indexes (bit fields mapped to indexes) 0 to 2 correspond to (indicate) TPMI=0 to 2 in one layer, respectively. Bit field index 3 may be a reserved bit.

[0102] Also, if the codebook subsets are non-coherent and the maximum rank number is 2, bit field indices 0 to 2 correspond to (indicate) TPMI=0 to 2, respectively, in layer 1, and bit field indices 3 to 5 correspond to TPMI=3 to 5, respectively, in layer 2. Bit field indices 6 and 7 may be reserved bits.

[0103] Also, if the codebook subsets are non-coherent and the maximum rank number is 3, bit field indexes 0 to 2 correspond to (indicate) TPMI=0 to 2, respectively, in layer 1, bit field indexes 3 to 5 correspond to TPMI=3 to 5, respectively, in layer 2, and bit field index 6 corresponds to TPMI=6 in layer 3. Bit field index 7 may be a reserved bit.

[0104] As shown in FIG. 12, when the maximum rank number is 1, the number of bits required to indicate the TPMI is 2, and when the maximum rank number is 2 or 3, the number of bits required to indicate the TPMI is 3.

[0105] Based on the precoding information field of the DCI (e.g., DCI format 0_1 / 0_2) that schedules the PUSCH, the UE can appropriately determine / apply the TPMI and number of layers (transmission rank) for the PUSCH, i.e., the precoder for each transmission rank using three antenna ports.

[0106] <Enable codebook for 3TX UE> FIG. 13 is a diagram showing an example of the correspondence between the field values ​​of the precoding information and the number of layers, and the number of layers and TPMI.

[0107] Although the above example illustrates a case where the transform precoder is disabled, the example is not limited to this. Depending on the UE capability, the transform precoder may be enabled / configured for a 3TX UE (e.g., max rank=1).

[0108] As shown in Figure 13, when the codebook subset is non-coherent and the transform precoder is enabled, bit field indexes 0 to 2 correspond to (indicate) TPMI = 0 to 2 in one layer, respectively. Bit field index 3 may be a reserved bit.

[0109] As shown in FIG. 13, a dedicated correspondence relationship (table) may be defined depending on the case where the transform precoder is valid, but the correspondence relationship for the maximum rank number=1 shown in FIG. 12 may also be referenced (reused).

[0110] As described above, according to FIG. 13 (or FIG. 12), when the maximum rank number is 1 and the transform precoder is enabled, the number of bits required to indicate the TPMI is 2 bits.

[0111] In addition, the UE (3TX UE) may report whether it supports a transform precoder for codebook-based PUSCH with rank=1 through UE capability signaling.

[0112] (analysis) Incidentally, in addition to codebook-based (3TX codebook-based) UL transmission with three antenna ports, non-codebook-based (3TX non-codebook-based) UL transmission with three antenna ports is being considered.

[0113] Some of the provisions of the 3TX codebook base can also be applied / extended to the 3TX non-codebook base.

[0114] For example, the following provisions can be mentioned:

[0115] In codebook-based UL transmission by a 3TX UE, when one PTRS port is configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the indication indicating the relationship between PTRS and DMRS is as follows:

[0116] 2-bit instruction. for example, A value of 0 indicates the first scheduled DMRS port; A value of 1 indicates a second scheduled DMRS port; A value of 2 indicates the third scheduled DMRS port; A value of 3 may indicate reserved.

[0117] That is, in STRP, when one PTRS port is configured, the [Code Point] value = 3 is not used (corresponding to reserved) compared to the existing specifications.

[0118] In addition, in non-codebook-based UL transmission by a 3TX UE, when two PTRS ports are configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the indication (PTRS-DMRS related field) indicating the relationship between the PTRS and DMRS for two DMRS ports sharing one PTRS port is as follows:

[0119] A Most Significant Bit (MSB) value of 0 may indicate the first DMRS port sharing the PTRS port, and a MSB value of 1 may indicate the second DMRS port sharing the PTRS port.

[0120] Thus, in STRP, when two PTRS ports are configured, the least significant bit (LSB) is not used compared to the existing specifications, i.e., the PTRS-DMRS related field is reduced from 2 bits to 1 bit.

[0121] In addition, in the case of codebook-based MTRP PUSCH repetitive transmission by 3TX UE, the indication indicating the relationship between PTRS and DMRS (PTRS-DMRS association field) is as follows:

[0122] If one PTRS port is configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the existing (e.g., for Rel. 17) MTRP TDM repeat transmission provisions may apply.

[0123] When two PTRS ports are configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig) and the maximum rank number is 2,3, the second PTRS-DMRS association field (1 bit) can be used to indicate the relationship between the PTRS port and the DMRS port of the second SRS resource set (i.e., the second TRP).

[0124] In the case of MTRP, the difference from the existing version (Rel.17) exists in the case where two PTRS ports are set.

[0125] More specifically, in the existing MTRP, when the maximum rank number is 3 or 4, two PTRS-DMRS related fields are indicated, each consisting of 2 bits.

[0126] When the maximum rank number is 2, one PTRS-DMRS association field is indicated, and the two bits, MSB and LSB, can be applied to two TRPs, respectively.

[0127] In 3TX, when the maximum rank number is 2,3, two PTRS-DMRS related fields are indicated, each consisting of 1 bit.

[0128] In addition, if one PTRS port is configured, the existing MTRP provisions may be applied for 3TX.

[0129] As such, UE behavior regarding the correspondence between PTRS and DMRS of non-codebook-based PUSCH may differ between 3TX UEs and legacy UEs in the following respects. ·STRP when one PTRS port is configured. -STRP when two PTRS ports are configured. · MTRP when two PTRS ports are configured.

[0130] For codebook-based UL transmission, a new RRC parameter may be introduced for each SRS resource set to enable 3TX, and the new RRC parameter is configured to enable muting of one port (e.g., port 1003) of the 4-port SRS.

[0131] Similarly, in non-codebook-based UL transmission, it is necessary to consider how to enable 3TX and clarify the UE behavior according to the method.

[0132] For example, in the existing specifications, there is no RRC parameter to enable non-codebook-based UL transmission for 4TX / 8TX. Therefore, even if three SRS resources (used as NCBs) are configured, it is not clear whether the network (base station / gNB) intends to configure a 3TX UE or a 4TX / 8TX UE.

[0133] However, the UE operation for non-codebook based UL transmission for 3TX is different from that for 4TX / 8TX, so it is necessary to distinguish between the operation for 3TX and the operation for 4TX / 8TX.

[0134] As mentioned above, the various regulations for realizing 3TX are not yet fully clarified. Without these, it may be difficult to properly control UL transmission using three antenna ports.

[0135] Therefore, the present inventors have focused on the existence of such cases and conceived the wireless communication method according to the present disclosure.

[0136] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

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

[0138] In the present disclosure, "A / B" and "at least one of A and B" may be interpreted interchangeably. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0139] In the present disclosure, terms such as notify, activate, deactivate, indicate (or indicate), select, configure, update, and determine may be interchangeable. In the present disclosure, terms such as support, control, controllable, operate, and operate may be interchangeable.

[0140] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In the present disclosure, Medium Access Control (MAC) control elements (CEs), update commands, activation / deactivation commands, etc. may be interchangeable.

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

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

[0143] In the present disclosure, physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), and the like.

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

[0145] In this disclosure, the terms panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmitting entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relation, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), antenna port (e.g., Demodulation Reference Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, Quasi-Co-Location (QCL), QCL assumption, etc. may be read as interchangeable.

[0146] In the present disclosure, TPMI and TPMI index may be interchangeable. Port and antenna port may be interchangeable. 8TX (8 transmission) may mean 8 ports and 8 antenna ports. Port / antenna port may mean a port / antenna port for UL (e.g., SRS / PUSCH) transmission. In the present disclosure, SRS resource set and resource set may be interchangeable. Coherent group and SRS resource set may be interchangeable.

[0147] This disclosure mainly describes 3TX, but the same applies to 5TX, 6TX, 7TX, 8 or more TX, 4 or less TX, etc. In the following embodiments, "3" may be read as "n (n is any integer)", and in this case, those skilled in the art can appropriately read the number of layers / ports, etc., described assuming the maximum value is "3", assuming the maximum value is "n".

[0148] It should be noted that in this disclosure, "having the capability of..." may be read interchangeably as "supporting / reporting the capability of...".

[0149] In the present disclosure, the terms rank, transmission rank, number of layers, and number of antenna ports may be interchangeable. Furthermore, the application of one codeword and the number of layers being four or less may be interchangeable. The application of two codewords and the number of layers being more than four may be interchangeable.

[0150] In the present disclosure, a table may be read interchangeably as one or more tables.

[0151] In the present disclosure, the terms table, mapping, correspondence, association, and association may be read interchangeably.

[0152] Furthermore, DCI in the following embodiments may refer to DCI that schedules at least one of PUSCH and PDSCH (for example, DCI format 0_x, 1_x (where x is an integer)). Furthermore, the following embodiments are based on the premise of codebook-based transmission (PUSCH), but are not limited to this.

[0153] (Wireless communication method) The embodiments of the present disclosure can be broadly categorized as follows. First embodiment: Higher layer signaling (RRC parameters) to enable non-codebook based UL transmission for 3TX. Second embodiment: Relationship between PTRS and DMRS in non-codebook based UL transmission for 3TX. Each embodiment will be described below based on these.

[0154] In the present disclosure, each embodiment / option may be applied alone or in combination with other embodiments / options.

[0155] In the present disclosure, the association between the precoding matrix W and the TPMI index may be defined in Specification 1 for Physical Channels and Modulation (Physical channels and modulation / Uplink / Physical channels / Physical uplink shared channel / Precoding). In the present disclosure, the association, table Px, TMPI table, precoding matrix table, and precoder table may be interchangeable.

[0156] In the present disclosure, the association between the precoding information (TPMI) and the number of layers (TRI) and the index (precoding information field value) may be defined in Specification 2 for Multiplexing and Channel Coding (Multiplexing and Channel Coding / Downlink Transport Channels and Control Information / Downlink Control Information / DCI Formats / DCI Format 0_1). In the present disclosure, the association, table Dx, TRI / TPMI indication table, DCI indication table, and precoding information table may be interchangeable.

[0157] In the present disclosure, the terms precoding matrix and precoder may be interpreted as interchangeable.

[0158] In the present disclosure, TPMI, TPMI field, and precoding information may be interpreted as interchangeable.

[0159] In the following embodiments, the precoding matrix / precoder may refer to a full / partial / non-coherent precoder.

[0160] In the following embodiments, a number (for example, 0, 1, 2, etc.) corresponding to a certain index (for example, TPMI index, antenna port index) may be replaced with a number with a # (for example, #0, #1, #2, etc.).

[0161] The UE may control UL transmission using three antenna ports (3TX UL transmission) by applying each embodiment described later. The NW / BS / gNB may provide / transmit to the UE settings / instructions, etc., for the UE to realize this control. Furthermore, the NW / BS / gNB may perform various controls to receive the UL transmission from the UE.

[0162] The 3TX UL transmission of the present disclosure is not limited to single / multiple TRP PUSCH, but can also be applied to multi-TRP PUSCH repetition in Rel. 17 or STxMP SFN / SDM PUSCH in Rel. 18.

[0163] First Embodiment The first embodiment relates to higher layer signaling (RRC parameters / higher layer parameters) enabling non-codebook based UL transmission for 3TX.

[0164] In this disclosure, unless otherwise specified, 3TX UL transmission may refer to non-codebook-based UL transmission, i.e., 3TX UE may refer to a UE that supports non-codebook-based UL transmission for 3TX.

[0165] In the present disclosure, non-codebook based 3TX UL transmission and non-codebook based UL transmission for 3TX may be read interchangeably.

[0166] A new RRC parameter may be specified / defined to enable non-codebook based UL transmission for 3TX.

[0167] New RRC parameters may be provided for each SRS resource set for SRS resource sets whose usage is set to non-codebook (NCB).

[0168] The new RRC parameters may be provided not only per SRS resource set but also per BWP / CC / cell.

[0169] When two SRS resource sets are configured with non-codebook usage (i.e., MTRP), the UE may expect the above-mentioned novel RRC parameters to be configured the same for the two SRS resource sets.

[0170] That is, in this case, the UE may assume / expect that the configuration regarding enabling non-codebook based UL transmission for 3TX is the same for the two SRS resource sets.

[0171] (Variation) If the new RRC parameters enable 3TX UL transmission for one of the SRS resource sets, the UE may assume / expect that 3TX UL transmission is enabled.

[0172] The above content may be extended / applied not only to non-codebook-based but also to codebook-based UL transmission. That is, the above-mentioned "non-codebook (NCB) usage" may be read as "codebook (CB) usage."

[0173] That is, when two SRS resource sets with usage set to codebook (i.e., MTRP) are configured, the UE may expect the RRC parameters enabling 3TX UL transmission (in which one port of the 4-port SRS (e.g., port 1003) is muted) to be configured the same for the two SRS resource sets.

[0174] That is, in this case, the UE may assume / expect that the configuration regarding enabling codebook-based UL transmission for 3TX is the same for the two SRS resource sets.

[0175] According to this embodiment, a method for enabling non-codebook-based UL transmission for 3TX is clarified, and the UE can appropriately support the operation related to non-codebook-based UL transmission for 3TX based on the method.

[0176] <Second embodiment> The second embodiment relates to the relationship between PTRS and DMRS in non-codebook based UL transmission for 3TX.

[0177] <<Aspect 2-1>> In non-codebook based UL transmission, when 3TX UL transmission is enabled by the above-mentioned new RRC parameters, the UE behavior regarding the relationship between PTRS and DMRS may be based on at least one of the following:

[0178] The above-mentioned phrase "when 3TX UL transmission is enabled by new RRC parameters in non-codebook-based UL transmission" may be read as "when the UE reports capability information supporting non-codebook-based 3TX UL transmission."

[0179] 14A to 14C are diagrams illustrating an example of a correspondence relationship between a PTRS and a DMRS in non-codebook-based 3TX UL transmission of the present disclosure.

[0180] When one PTRS port is configured in the STRP, the indication indicating the relationship between the PTRS and the DMRS (PTRS-DMRS association field) may be configured with two bits as follows: The indication may be included in DCI format 0_1 / 0_2, or may be an indication for each cell in DCI format 0_3.

[0181] For example, as shown in FIG. 14A, A value of 0 indicates the first scheduled DMRS port; A value of 1 indicates a second scheduled DMRS port; A value of 2 indicates the third scheduled DMRS port; A value of 3 may indicate reserved.

[0182] In addition, when two PTRS ports are configured in the STRP, the indication indicating the relationship between the PTRS and the DMRS (PTRS-DMRS association field) may be configured with one bit as follows: The indication may be included in DCI format 0_1 / 0_2, or may be an indication for each cell in DCI format 0_3.

[0183] For example, as shown in FIG. 14B, an MSB value of 0 may indicate the first DMRS port that shares the PTRS port, and an MSB value of 1 may indicate the second DMRS port that shares the PTRS port.

[0184] In addition, in an MTRP, when two PTRS ports are configured and the maximum rank number is 2 or 3, the indication indicating the relationship between the PTRS and DMRS (PTRS-DMRS association field) may be configured with one bit as follows: The indication may be included in DCI format 0_1 / 0_2, or may be an indication for each cell in DCI format 0_3.

[0185] For example, as shown in FIG. 14C, an MSB value of 0 may indicate the first DMRS port that shares the PTRS port, and an MSB value of 1 may indicate the second DMRS port that shares the PTRS port.

[0186] That is, when two PTRS ports are set, the same correspondence relationship may be applied to STRP and MTRP (when the maximum rank number is 2, 3) (the correspondence relationship in Figures 14B and 14C may be the same).

[0187] If none of the above applies (i.e., 3TX UL transmission is not enabled by new RRC parameters or the UE does not report capability information supporting non-codebook-based 3TX UL transmission), the UE behavior regarding the relationship between PTRS and DMRS may be based on existing specifications.

[0188] <<Aspect 2-2>> The above-described example 2-1 may be extended / applied to codebook-based UL transmission. That is, "non-codebook-based" in example 2-1 may be read as "codebook-based."

[0189] In codebook-based UL transmission, when 3TX UL transmission is enabled by the new RRC parameters described above, the UE behavior regarding the relationship between PTRS and DMRS may be based on at least one of the following:

[0190] "When 3TX UL transmission is enabled by new RRC parameters in codebook-based UL transmission" may be read as "when the UE reports capability information supporting codebook-based 3TX UL transmission."

[0191] 15A to 15C are diagrams illustrating an example of a correspondence relationship between a PTRS and a DMRS in codebook-based 3TX UL transmission of the present disclosure.

[0192] When one PTRS port is configured in the STRP, the indication indicating the relationship between the PTRS and the DMRS (PTRS-DMRS association field) may be configured with two bits as follows: The indication may be included in DCI format 0_1 / 0_2, or may be an indication for each cell in DCI format 0_3.

[0193] For example, as shown in FIG. 15A, A value of 0 indicates the first scheduled DMRS port; A value of 1 indicates a second scheduled DMRS port; A value of 2 indicates the third scheduled DMRS port; A value of 3 may indicate reserved.

[0194] In addition, when two PTRS ports are configured in the STRP, the indication indicating the relationship between the PTRS and the DMRS (PTRS-DMRS association field) may be configured with one bit as follows: The indication may be included in DCI format 0_1 / 0_2, or may be an indication for each cell in DCI format 0_3.

[0195] For example, as shown in FIG. 15B, a value of 0 may indicate a first DMRS port that shares PTRS port 0, and a value of 1 may indicate a second DMRS port that shares PTRS port 1.

[0196] In addition, in an MTRP, when two PTRS ports are configured and the maximum rank number is 2 or 3, the indication indicating the relationship between the PTRS and DMRS (PTRS-DMRS association field) may be configured with one bit as follows: The indication may be included in DCI format 0_1 / 0_2, or may be an indication for each cell in DCI format 0_3.

[0197] For example, as shown in FIG. 15C, a value of 0 may indicate a first DMRS port that shares PTRS port 0, and a value of 1 may indicate a second DMRS port that shares PTRS port 1.

[0198] That is, when two PTRS ports are set, the same correspondence relationship may be applied to STRP and MTRP (when the maximum rank number is 2, 3) (the correspondence relationship in Figures 15B and 15C may be the same).

[0199] If none of the above applies (i.e., 3TX UL transmission is not enabled by new RRC parameters or the UE does not report capability information supporting codebook-based 3TX UL transmission), the UE behavior regarding the relationship between PTRS and DMRS may be based on existing specifications.

[0200] <<Specification description example>> Examples of specification descriptions of the present disclosure are listed below: Figures 16A to 16C are diagrams showing examples of correspondence relationships between PTRSs and DMRSs in 3TX UL transmission of the present disclosure.

[0201] For example, Figure 16A may show the PTRS-DMRS relationship for codebook-based / non-codebook-based 3TX UL transmission with one PTRS port configured, Figure 16B may show the PTRS-DMRS relationship for codebook-based 3TX UL transmission with two PTRS ports configured, and Figure 16C may show the PTRS-DMRS relationship for non-codebook-based 3TX UL transmission with two PTRS ports configured.

[0202] (DCI format 0_1) The number of bits in the PTRS-DMRS related field is determined as follows.

[0203] It is a 0 bit if any of the following is true: - When the PTRS setting (PTRS-UplinkConfig) is not set for one of the specific mapping types (dmrs-UplinkForPUSCH-MappingTypeA, dmrs-UplinkForPUSCH-MappingTypeB) and the transform precoder is disabled. -When the transform precoder is enabled. - When the maximum number of ranks (maxRank) is 1 and the multipanel scheme parameter (multipanelScheme) is not set. · When the maximum rank number = 1 and the maximum rank number of SFN (maxRankSfn) = 1. ·When two PTRS ports are configured by the maximum number of ports for SDM (maxNrofPortsforSdm), the maximum number of ranks = 1 and the maximum number of ranks for SDM (maxRankSdm) = 1.

[0204] Otherwise, it is either 1, 2 or 4 bits as shown below. A table / correspondence defined in the specification (see e.g. Figures 16A to 16C) is used to indicate the correspondence between PTRS and DMRS. The DMRS port is indicated by the antenna port field.

[0205] ((3TX UL transmission is not enabled in STRP)) If one PTRS port / two PTRS ports are configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the SRS resource set indicator field is not present, or the SRS resource set indicator field is present and its value is equal to "00" or "01", the maximum rank number is 4, new RRC parameters enabling codebook-based 3TX UL are not configured, and new RRC parameters enabling non-codebook-based 3TX UL are not configured, this bit is 2 bits.

[0206] This field indicates the association of the PTRS port and the DMRS port corresponding to the SRS resource indicator field / precoding information and the layer number field according to a specific table / correspondence.

[0207] ((When one PTRS port is configured in STRP and 3TX UL transmission is enabled)) This bit is 2 bits if one PTRS port is configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the SRS resource set indicator field is not present, or the SRS resource set indicator field is present and its value is equal to "00" or "01", the maximum rank number is 4, and new RRC parameters enabling codebook-based 3TX UL are configured, or new RRC parameters enabling non-codebook-based 3TX UL are configured.

[0208] This field indicates the association of PTRS ports and DMRS ports corresponding to the SRS resource indicator field / precoding information and layer number field according to a specific table / correspondence (see, for example, FIG. 16A).

[0209] ((When two PTRS ports are configured in the STRP and 3TX UL transmission is enabled)) This bit is 1 if two PTRS ports are configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the SRS resource set indicator field is not present, or the SRS resource set indicator field is present and its value is equal to "00" or "01", the maximum rank number is 4, and new RRC parameters enabling codebook-based 3TX UL are configured, or new RRC parameters enabling non-codebook-based 3TX UL are configured.

[0210] This field indicates the association of PTRS ports and DMRS ports corresponding to the SRS resource indicator field / precoding information and layer number field according to a specific table / correspondence (see, for example, Figure 16B / Figure 16C).

[0211] ((When one PTRS port is configured in MTRP and the maximum rank number is 3,4 regardless of whether 3TX UL transmission is enabled)) If one PTRS port is configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the SRS resource set indicator field exists and its value is equal to "10" or "11", the maximum number of ranks is 3 or 4, and the parameter related to the multipanel scheme (multipanelScheme) is not set, then this is 2 bits.

[0212] This field indicates the association of the PTRS port and the DMRS port corresponding to the SRS resource indicator field / precoding information and the layer number field according to a specific table / correspondence.

[0213] ((2 PTRS ports configured in MTRP, max rank = 3,4, 3TX UL transmission not enabled)) If two PTRS ports are configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the SRS resource set indicator field exists and its value is equal to "10" or "11", the maximum rank number is 3 or 4, the parameter related to the multipanel scheme (multipanelScheme) is not configured, new RRC parameters enabling codebook-based 3TX UL are not configured, and new RRC parameters enabling non-codebook-based 3TX UL are not configured, this bit is 2 bits.

[0214] This field indicates the association of the PTRS port and the DMRS port corresponding to the SRS resource indicator field / precoding information and the layer number field according to a specific table / correspondence.

[0215] ((When one PTRS port is configured in MTRP and the maximum rank number is 2, regardless of whether 3TX UL transmission is enabled)) If one PTRS port is configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the SRS resource set indicator field exists and its value is equal to "10" or "11", the maximum number of ranks is 2, and the parameter related to the multipanel scheme (multipanelScheme) is not set, then this is 2 bits.

[0216] The MSB of this field indicates the association of the PTRS port and DMRS port corresponding to the SRS resource indicator field / precoding information and layer number field according to a specific table / correspondence.

[0217] The LSB of this field indicates the association of the PTRS port and the DMRS port corresponding to the second SRS resource indicator field / second precoding information and layer number field according to a specific table / correspondence relationship.

[0218] ((When two PTRS ports are configured in the MTRP, the maximum rank number is 2, and 3TX UL transmission is not enabled)) If two PTRS ports are configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the SRS resource set indicator field is present and its value is equal to "10" or "11", the maximum number of ranks is 2, the parameter related to the multipanel scheme (multipanelScheme) is not configured, new RRC parameters enabling codebook-based 3TX UL are not configured, and new RRC parameters enabling non-codebook-based 3TX UL are not configured, then this bit is 2.

[0219] The MSB of this field indicates the association of the PTRS port and DMRS port corresponding to the SRS resource indicator field / precoding information and layer number field according to a specific table / correspondence.

[0220] The LSB of this field indicates the association of the PTRS port and the DMRS port corresponding to the second SRS resource indicator field / second precoding information and layer number field according to a specific table / correspondence relationship.

[0221] ((When two PTRS ports are configured in MTRP, maximum rank number = 2,3, and 3TX UL transmission is enabled)) This bit is 1 if two PTRS ports are configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the SRS resource set indicator field exists and its value is equal to "10" or "11", the maximum number of ranks is 2, 3, the parameter related to the multipanel scheme (multipanelScheme) is not configured, and new RRC parameters enabling codebook-based 3TX UL are configured, or new RRC parameters enabling non-codebook-based 3TX UL are configured.

[0222] This field indicates the association of PTRS ports and DMRS ports corresponding to the SRS resource indicator field / precoding information and layer number field according to a specific table / correspondence (see, for example, Figure 16B / Figure 16C).

[0223] ((Second PTRS-DMRS related field)) The number of bits of the second PTRS-DMRS related field is determined as follows.

[0224] If the PTRS-DMRS related field and the SRS resource set indicator field are present and the maximum rank is greater than 2, the parameters related to the multipanel scheme (multipanelScheme) are not configured, the new RRC parameters enabling codebook-based 3TX UL are not configured, and the new RRC parameters enabling non-codebook-based 3TX UL are not configured, then this bit is 2 bits.

[0225] This bit is 2 if the PTRS-DMRS related fields and the SRS resource set indicator field are present and the maximum rank number is greater than 2, the parameters related to the multipanel scheme (multipanelScheme) are not set, new RRC parameters enabling codebook-based 3TX UL are set, or new RRC parameters enabling non-codebook-based 3TX UL are set, and one PTRS port is configured by the parameter related to the maximum number of ports (maxNrofPorts) in the PTRS configuration (PTRS-UplinkConfig).

[0226] This bit is 1 if the PTRS-DMRS related fields and the SRS resource set indicator field are present, and the maximum rank number is 2 or 3, and the parameter related to the multipanel scheme (multipanelScheme) is not set, and new RRC parameters enabling codebook-based 3TX UL are set, or new RRC parameters enabling non-codebook-based 3TX UL are set, and two PTRS ports are configured by the parameter related to the maximum number of ports (maxNrofPorts) in the PTRS configuration (PTRS-UplinkConfig).

[0227] If none of the above applies, it is a 0 bit.

[0228] A specific table / correspondence (see, for example, Figure 16B / Figure 16C) is used to indicate the association between the PTRS port and the DMRS port corresponding to the second SRS resource indicator field / second precoding information and layer number field when one / two PTRS ports are configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig) and the DMRS port is indicated by the antenna port field.

[0229] (DCI format 0_2) The number of bits in the PTRS-DMRS related field is determined as follows.

[0230] It is a 0 bit if any of the following is true: - When the PTRS setting (PTRS-UplinkConfig) is not set for one of the specific mapping types (dmrs-UplinkForPUSCH-MappingTypeA, dmrs-UplinkForPUSCH-MappingTypeB) and the transform precoder is disabled. -When the transform precoder is enabled. - When the maximum number of ranks (maxRankDCI-0-2) = 1 and the parameter related to the multi-panel scheme (multipanelScheme) is not set. · When the maximum rank number (maxRankDCI-0-2) = 1 and the maximum rank number of SFN (maxRankSfnDCI-0-2) = 1. ·When two PTRS ports are configured by the maximum number of ports for SDM (maxNrofPortsforSdm), the maximum number of ranks (maxRankDCI-0-2) = 1 and the maximum number of ranks for SDM (maxRankSdmDCI-0-2) = 1.

[0231] Otherwise, it is either 1 or 2 bits as shown below. A table / correspondence defined in the specification (see e.g. Figures 16A to 16C) is used to indicate the correspondence between PTRS and DMRS. The DMRS port is indicated by the antenna port field.

[0232] ((3TX UL transmission is not enabled in STRP)) If one PTRS port / two PTRS ports are configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the SRS resource set indicator field is not present, or the SRS resource set indicator field is present and its value is equal to "00" or "01", the maximum number of ranks (maxRankDCI-0-2) = 4, no new RRC parameters enabling codebook-based 3TX UL are configured, and no new RRC parameters enabling non-codebook-based 3TX UL are configured, this bit is 2 bits.

[0233] This field indicates the association of the PTRS port and the DMRS port corresponding to the SRS resource indicator field / precoding information and the layer number field according to a specific table / correspondence.

[0234] ((When one PTRS port is configured in STRP and 3TX UL transmission is enabled)) This bit is 2 bits if one PTRS port is configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the SRS resource set indicator field is not present, or the SRS resource set indicator field is present and its value is equal to "00" or "01", the maximum number of ranks (maxRankDCI-0-2) = 4, and new RRC parameters enabling codebook-based 3TX UL are configured, or new RRC parameters enabling non-codebook-based 3TX UL are configured.

[0235] This field indicates the association of PTRS ports and DMRS ports corresponding to the SRS resource indicator field / precoding information and layer number field according to a specific table / correspondence (see, for example, FIG. 16A).

[0236] ((When two PTRS ports are configured in the STRP and 3TX UL transmission is enabled)) This bit is 1 if two PTRS ports are configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the SRS resource set indicator field is not present, or the SRS resource set indicator field is present and its value is equal to "00" or "01", the maximum rank number (maxRankDCI-0-2) = 4, and new RRC parameters enabling codebook-based 3TX UL are configured, or new RRC parameters enabling non-codebook-based 3TX UL are configured.

[0237] This field indicates the association of PTRS ports and DMRS ports corresponding to the SRS resource indicator field / precoding information and layer number field according to a specific table / correspondence (see, for example, Figure 16B / Figure 16C).

[0238] ((When one PTRS port is configured in MTRP and the maximum rank number is 3,4 regardless of whether 3TX UL transmission is enabled)) If one PTRS port is configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the SRS resource set indicator field exists and its value is equal to "10" or "11", the maximum number of ranks (maxRankDCI-0-2) = 3, 4, and the parameter related to the multipanel scheme (multipanelScheme) is not set, then this is 2 bits.

[0239] This field indicates the association of the PTRS port and the DMRS port corresponding to the SRS resource indicator field / precoding information and the layer number field according to a specific table / correspondence.

[0240] ((2 PTRS ports configured in MTRP, max rank = 3,4, 3TX UL transmission not enabled)) If two PTRS ports are configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the SRS resource set indicator field exists and its value is equal to "10" or "11", the maximum number of ranks (maxRankDCI-0-2) = 3, 4, the parameter related to the multipanel scheme (multipanelScheme) is not configured, new RRC parameters enabling codebook-based 3TX UL are not configured, and new RRC parameters enabling non-codebook-based 3TX UL are not configured, this bit is 2 bits.

[0241] This field indicates the association of the PTRS port and the DMRS port corresponding to the SRS resource indicator field / precoding information and the layer number field according to a specific table / correspondence.

[0242] ((When one PTRS port is configured in MTRP and the maximum rank number is 2, regardless of whether 3TX UL transmission is enabled)) If one PTRS port is configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the SRS resource set indicator field exists and its value is equal to "10" or "11", the maximum number of ranks (maxRankDCI-0-2) = 2, and the parameter related to the multipanel scheme (multipanelScheme) is not set, then this is 2 bits.

[0243] The MSB of this field indicates the association of the PTRS port and DMRS port corresponding to the SRS resource indicator field / precoding information and layer number field according to a specific table / correspondence.

[0244] The LSB of this field indicates the association of the PTRS port and the DMRS port corresponding to the second SRS resource indicator field / second precoding information and layer number field according to a specific table / correspondence relationship.

[0245] ((When two PTRS ports are configured in the MTRP, the maximum rank number is 2, and 3TX UL transmission is not enabled)) If two PTRS ports are configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the SRS resource set indicator field exists and its value is equal to "10" or "11", the maximum number of ranks (maxRankDCI-0-2) = 2, the parameter related to the multipanel scheme (multipanelScheme) is not configured, new RRC parameters enabling codebook-based 3TX UL are not configured, and new RRC parameters enabling non-codebook-based 3TX UL are not configured, this bit is 2 bits.

[0246] The MSB of this field indicates the association of the PTRS port and DMRS port corresponding to the SRS resource indicator field / precoding information and layer number field according to a specific table / correspondence.

[0247] The LSB of this field indicates the association of the PTRS port and the DMRS port corresponding to the second SRS resource indicator field / second precoding information and layer number field according to a specific table / correspondence relationship.

[0248] ((When two PTRS ports are configured in MTRP, maximum rank number = 2,3, and 3TX UL transmission is enabled)) This bit is 1 if two PTRS ports are configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the SRS resource set indicator field is present and its value is equal to "10" or "11", the maximum number of ranks (maxRankDCI-0-2) = 2,3, the parameter related to the multipanel scheme (multipanelScheme) is not configured, and new RRC parameters enabling codebook-based 3TX UL are configured, or new RRC parameters enabling non-codebook-based 3TX UL are configured.

[0249] This field indicates the association of PTRS ports and DMRS ports corresponding to the SRS resource indicator field / precoding information and layer number field according to a specific table / correspondence (see, for example, Figure 16B / Figure 16C).

[0250] ((Second PTRS-DMRS related field)) The number of bits of the second PTRS-DMRS related field is determined as follows.

[0251] If the PTRS-DMRS related field and the SRS resource set indicator field are present, and the maximum rank number (maxRankDCI-0-2) is greater than 2, and the parameters related to the multi-panel scheme (multipanelScheme) are not set, and the new RRC parameters enabling codebook-based 3TX UL are not set, and the new RRC parameters enabling non-codebook-based 3TX UL are not set, then this bit is 2 bits.

[0252] This bit is 2 if the PTRS-DMRS related fields and the SRS resource set indicator field are present, and the maximum rank number (maxRankDCI-0-2) is greater than 2, the parameters related to the multipanel scheme (multipanelScheme) are not configured, new RRC parameters enabling codebook-based 3TX UL are configured, or new RRC parameters enabling non-codebook-based 3TX UL are configured, and one PTRS port is configured by the parameter related to the maximum number of ports (maxNrofPorts) in the PTRS configuration (PTRS-UplinkConfig).

[0253] This bit is 1 bit if the PTRS-DMRS related fields and the SRS resource set indicator field are present, and the maximum rank number (maxRankDCI-0-2) = 2, 3, the parameter related to the multipanel scheme (multipanelScheme) is not set, new RRC parameters enabling codebook-based 3TX UL are set, or new RRC parameters enabling non-codebook-based 3TX UL are set, and two PTRS ports are configured by the parameter related to the maximum number of ports (maxNrofPorts) in the PTRS configuration (PTRS-UplinkConfig).

[0254] If none of the above applies, it is a 0 bit.

[0255] A specific table / correspondence is used to indicate the association between the PTRS port and the DMRS port corresponding to the second SRS resource indicator field / second precoding information and layer number field when one / two PTRS ports are configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig) and the DMRS port is indicated by the antenna port field.

[0256] (DCI format 0_3) The number of bits in the PTRS-DMRS related field is determined as follows.

[0257] The block numbers are block number 1, block number 2, ..., block number N UL cell may be represented by:

[0258] Each block may correspond to the PTRS-DMRS related information of a cell. These blocks may be arranged according to the ascending order of the serving cell index. For example, block number 1 corresponds to the PTRS-DMRS related information of the cell with the smallest serving cell index. The number of bits of each block may be defined as follows:

[0259] It is a 0 bit if any of the following is true: When the PTRS configuration (PTRS-UplinkConfig) is not set for one of the specific mapping types (dmrs-UplinkForPUSCH-MappingTypeA, dmrs-UplinkForPUSCH-MappingTypeB) and the transform precoder is disabled, or the transform precoder is enabled, or the maximum rank number (maxRankDCI) = 1.

[0260] Otherwise, it is either 1 or 2 bits, as shown below. The table / correspondence defined in the specification (see, for example, Figures 16A to 16C) is used to indicate the association between the PTRS port and the DMRS port corresponding to the SRS resource indicator field / precoding information and number of layers field when one / two PTRS ports are configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig) and the DMRS port is indicated by the antenna port field.

[0261] If 1 PTRS port / 2 PTRS ports are configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), and new RRC parameters enabling codebook-based 3TX UL are not configured, and new RRC parameters enabling non-codebook-based 3TX UL are not configured, this bit is 2.

[0262] This field indicates the association of the PTRS port and the DMRS port corresponding to the SRS resource indicator field / precoding information and the layer number field according to a specific table / correspondence.

[0263] This is 2 bits if one PTRS port is configured by the parameter related to the maximum number of ports (maxNrofPorts) in the PTRS configuration (PTRS-UplinkConfig) and new RRC parameters that enable codebook-based 3TX UL are configured, or new RRC parameters that enable non-codebook-based 3TX UL are configured.

[0264] This field indicates the association between the corresponding PTRS port and DMRS port according to a particular table / correspondence (e.g., see FIG. 16A).

[0265] This bit is 1 if two PTRS ports are configured by the parameter related to the maximum number of ports (maxNrofPorts) in the PTRS configuration (PTRS-UplinkConfig) and new RRC parameters that enable codebook-based 3TX UL are configured, or new RRC parameters that enable non-codebook-based 3TX UL are configured.

[0266] This field indicates the association between the corresponding PTRS port and DMRS port according to a specific table / correspondence (see, for example, Figure 16B / Figure 16C).

[0267] According to this embodiment, the method for indicating the correspondence relationship between PTRS and DMRS for 3TX UL transmission is clarified. The UE can appropriately control 3TX UL transmission based on this indication.

[0268] <Others> In the present disclosure, setting / not setting a new RRC parameter for enabling codebook-based / non-codebook-based 3TX UL transmission may be mutually read as the UE reporting / not reporting the ability information to support codebook-based / non-codebook-based 3TX UL transmission.

[0269] <Supplement> <<Notification of Information to the UE>> Notification of any information from [a network (NW) (for example, a base station (BS))] to the UE in the above-described embodiment (in other words, reception of any information from the BS by the UE) may be performed using physical layer signaling (for example, DCI), upper layer signaling (for example, RRC signaling, MAC CE), a specific signal / channel (for example, PDCCH, PDSCH, reference signal), or a combination thereof.

[0270] When the above notification is performed by MAC CE, the MAC CE may be identified by including a new logical channel ID (LCID) that is not defined in the existing standard in the MAC sub-header.

[0271] When the above notification is performed by DCI, the above notification may be performed based on a specific field of the DCI, a radio network temporary identifier (RNTI) used for scrambling cyclic redundancy check (CRC) bits assigned to the DCI, the format of the DCI, and the like.

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

[0273] <<Notification of Information from UE>> The notification of any information from the UE to the [NW] (in other words, the transmission / reporting of any information from the UE to the BS) in the above-described embodiments may be performed using physical layer signaling (e.g., UCI), upper layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

[0274] When the above notification is performed by MAC CE, the MAC CE may be identified by including a new LCID not defined in the existing standard in the MAC sub-header.

[0275] When the above notification is performed by UCI, the above notification may be transmitted using PUCCH or PUSCH.

[0276] Also, the notification of any information from the UE in the above-described embodiments may be performed periodically, semi-persistently, or aperiodically.

[0277] <<Regarding Application of Each Embodiment>> In the UE / BS, specific (one or more) processes / operations / controls / assumptions / information regarding at least one of the above-described embodiments may be applied (used) when any one or a plurality of the following conditions are satisfied: · An upper layer parameter indicating the above specific process / operation / control / assumption / information is set, · The above specific process / operation / control / assumption / information is determined based on a related upper layer parameter, · The above specific process / operation / control / assumption / information is specified / activated / triggered by MAC CE / DCI / UCI / resources / channels / RS, Reporting or supporting specific UE capabilities indicating (or relating to) the above specific processes / actions / controls / assumptions / information; · The application of the above specific processing / action / control / assumption / information is judged based on specific conditions.

[0278] The specific UE capabilities may indicate at least one of the following: Supporting specific processing / operations / control / information for at least one of the above embodiments; Support 3TX UL transmission; Supporting multiple different antenna layouts / number of antenna groups, Supports coherent groups, Supported coherence types (fully coherent / partially coherent / non-coherent). The number of supported precoder candidates.

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

[0280] Furthermore, the specific UE capability may be a capability that is applied across all duplexing methods (commonly regardless of the duplexing method), or may be a capability for each duplexing method (for example, Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

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

[0282] (Addendum) The following inventions are added regarding one embodiment of the present disclosure. [Appendix 1] a receiver for receiving higher layer parameters for non-codebook-based uplink (UL) transmission using three antenna ports (3TX); a controller that controls enabling of non-codebook based 3TX UL transmission based on the upper layer parameters. [Appendix 2] The terminal according to Supplementary Note 1, wherein the receiving unit receives the higher layer parameters for each measurement reference signal (SRS) resource set or for each cell. [Appendix 3] 3. The terminal according to claim 1, wherein, when the non-codebook-based 3TX UL transmission is enabled, the receiver receives downlink control information (DCI) including a field indicating a correspondence relationship between a phase tracking reference signal (PTRS) and a demodulation reference signal (DMRS). [Appendix 4] When the non-codebook-based 3TX UL transmission is enabled, the receiver receives downlink control information (DCI) including a field indicating a correspondence relationship between a phase tracking reference signal (PTRS) and a demodulation reference signal (DMRS); A terminal described in any one of Supplementary Note 1 to Supplementary Note 3, wherein the number of bits in the field varies depending on the number of PTRS ports to be set.

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

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

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

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

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

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

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

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

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

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

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

[0294] The core network 30 may include network functions (NFs) such as a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and an Operation, Administration and Maintenance (Management) (OAM). Note that a single network node may provide multiple functions. Furthermore, communication with an external network (e.g., the Internet) may be performed via the DN.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0327] The transceiver 120 may transmit higher layer parameters for non-codebook-based uplink (UL) transmission using three antenna ports (3TX). The controller 110 may control receiving, from the terminal, the enabled non-codebook-based 3TX UL transmission based on the higher layer parameters.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0344] The measurement unit 223 may derive channel measurements for CSI calculation based on the channel measurement resources. The channel measurement resources may be, for example, non-zero power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on the interference measurement resources. The interference measurement resources may be at least one of an NZP CSI-RS resource for interference measurement, a CSI-Interference Measurement (IM) resource, etc. Note that CSI-IM may be referred to as CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS. Note that in the present disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be interchangeably read as interchangeable.

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

[0346] The transceiver 220 may perform at least one of the processes of the transmitter / receiver in any of the above appendices.

[0347] The control unit 210 may execute at least one of the processes of the control unit in any of the above supplementary notes.

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

[0349] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As mentioned above, the implementation method of each is not particularly limited.

[0350] For example, a base station, a user terminal, or the like according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 20 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. The above-described base station 10 and user terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.

[0351] In this disclosure, terms such as apparatus, circuit, device, section, unit, etc. may be read interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0367] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

[0368] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

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

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

[0371] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0385] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.

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

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

[0388] Note that the physical layer signaling may be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be called an RRC message, such as an RRC connection setup message or an RRC connection reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

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

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

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

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

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

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

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

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

[0397] In addition, in the present disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable terms.

[0398] In addition, in the present disclosure, the terms TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc. may be read interchangeably.

[0399] Furthermore, in this disclosure, terms such as "QCL," "QCL assumptions," "QCL relationships," "QCL type information," "QCL properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

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

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

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

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

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

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

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

[0407] 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. Note that at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.

[0408] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.

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

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

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

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

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

[0414] The information service unit 59 is composed of various devices, such as a car navigation system, an audio system, speakers, a display, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 59 uses information acquired from external devices via the communication module 60 or the like to provide various information / services (for example, multimedia information / multimedia services) to the occupants of the vehicle 40.

[0415] The information service unit 59 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0416] The driving assistance system unit 64 is configured with various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Units (IMUs), Inertial Navigation Systems (INSs)), Artificial Intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driving assistance functions or autonomous driving functions.

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

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

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

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

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

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

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

[0424] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME) and a Serving-Gateway (S-GW)), or a combination thereof.

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

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

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

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

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

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

[0431] Furthermore, "determination" may be considered to be "determining" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "determining" some action. In the present disclosure, "determination" may be read interchangeably with the above-mentioned actions.

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

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

[0434] The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

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

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

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

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

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

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

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

[0442] In the present disclosure, terms such as "when A, B," "if A, (then) B," "B upon A," "B in response to A," "B based on A," "B during / while A," "B before A," "B at (the same time as) / on A," "B after A," "B since A," and "B until A" may be interchangeable. Note that A, B, and the like herein may be replaced with appropriate expressions, such as nouns, gerunds, and regular sentences, depending on the context. Note that the time difference between A and B may be nearly zero (immediately after or immediately before). A time offset may be applied to the time at which A occurs. For example, "A" may be interchangeable with "before / after the time offset at which A occurs." The time offset (eg, one or more symbols / slots) may be predefined or may be specified by the UE based on signaled information.

[0443] In the present disclosure, timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc. may be read interchangeably.

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

Claims

1. a receiver for receiving higher layer parameters for non-codebook-based uplink (UL) transmission utilizing three antenna ports (3TX); a controller that controls enabling of non-codebook based 3TX UL transmission based on the upper layer parameters.

2. The terminal according to claim 1 , wherein the receiving unit receives the higher layer parameters for each measurement reference signal (SRS) resource set or for each cell.

3. 2. The terminal according to claim 1, wherein, when the non-codebook-based 3TX UL transmission is enabled, the receiver receives downlink control information (DCI) including a field indicating a correspondence relationship between a phase tracking reference signal (PTRS) and a demodulation reference signal (DMRS).

4. When the non-codebook-based 3TX UL transmission is enabled, the receiver receives downlink control information (DCI) including a field indicating a correspondence relationship between a phase tracking reference signal (PTRS) and a demodulation reference signal (DMRS); The terminal according to claim 1 , wherein the number of bits in the field varies depending on the number of PTRS ports to be set.

5. receiving higher layer parameters for a non-codebook-based uplink (UL) transmission utilizing three antenna ports (3TX); and controlling enabling of non-codebook-based 3TX UL transmission based on the upper layer parameter.

6. a transmitter for transmitting higher layer parameters for non-codebook-based uplink (UL) transmission using three antenna ports (3TX); a controller that performs control to receive, from a terminal, the enabled non-codebook-based 3TX UL transmission based on the upper layer parameter.

Images