Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure is provided with: a reception unit that receives a codebook for uplink (UL) transmission using three antenna ports (3TX); and a control unit that controls the UL transmission on the basis of the codebook, the control unit determining, on the basis of an indication (SRI) for a measurement reference signal (SRS) resource set in the codebook, the transmission opportunity of the SRS resource.

Description

Technical Field

[0001] This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems. Background Technology

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

[0003] The study also explored subsequent systems to LTE (e.g., also known as the 5th generation mobile communication system (5G), 5G+, the 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.).

[0004] Existing technical documents

[0005] Non-patent literature

[0006] 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

[0007] The problem that the invention aims to solve

[0008] In Rel.15 NR, uplink (UL) multi-input multi-output (MIMO) transmission with a maximum of 4 layers is supported. Regarding future NRs, UL transmission with more than 4 layers is being investigated to achieve higher spectral efficiency. For example, for Rel.18 NR, maximum 6-rank transmission using 6 antenna ports and maximum 6- or 8-rank transmission using 8 antenna ports are being investigated.

[0009] On the other hand, after Rel.19, there may be situations where uplink full-power transmission is not supported. In such cases, since it is easy to implement codebook-based transmission using three antenna ports, the specification of incoherent UL codebooks (incoherent codebooks for UL) is being studied.

[0010] Therefore, one of the purposes of this disclosure is to provide, for example, a terminal, a wireless communication method, and a base station capable of appropriately controlling UL transmission using three antenna ports.

[0011] Methods for solving problems

[0012] One aspect of the present disclosure relates to a terminal comprising: a receiving unit for receiving a codebook for transmission via a (3TX) uplink (UL) using three antenna ports; and a control unit for controlling the UL transmission based on the codebook, the control unit determining the transmission opportunity of the SRS resource based on an indication (SRI) for a measurement reference signal (SRS) resource set in the codebook.

[0013] Invention Effects

[0014] According to one method of this disclosure, UL transmission can be appropriately controlled. Attached Figure Description

[0015] Figure 1 This is a diagram illustrating an example of a table of precoding matrices W used for single-layer (rank 1) transmission with four antenna ports in Rel.16 NR when the transformation precoder is invalid.

[0016] Figure 2 This is a diagram illustrating an example of a table of precoding matrices W used for 2-layer (rank 2) transmission with 4 antenna ports in Rel.16 NR when the transformation precoder is invalid.

[0017] Figure 3This is a diagram illustrating an example of a table of precoding matrices W used for 3-layer (rank 3) transmission with 4 antenna ports in Rel.16 NR when the transformation precoder is invalid.

[0018] Figure 4 This is a diagram illustrating an example of a table of precoding matrices W used for 4-layer (rank 4) transmission with 4 antenna ports in Rel.16 NR when the transformation precoder is invalid.

[0019] Figure 5A This is a diagram of an example of a table representing a precoding matrix W for a single-layer (rank 1) transmission using two antenna ports in Rel.16 NR. Figure 5B This is a diagram illustrating an example of a table of precoding matrices W used for 2-layer (rank 2) transmission with 2 antenna ports in Rel.16 NR when the transform precoding is invalid.

[0020] Figure 6 This is a diagram illustrating an example of the field values ​​for precoding information and layer number in Rel.16 NR, and the correspondence between them and the layer number and TPMI.

[0021] Figures 7A to 7C This is a diagram representing the SRI indication or second SRI indication when transmitting a codebook-based PUSCH in Rel.17.

[0022] Figure 8 This is a diagram showing an example of an antenna layout with 8 antenna ports.

[0023] Figure 9A and Figure 9B This is a diagram illustrating an example of the PTRS-DMRS association field in the existing specification.

[0024] Figure 10 This is a diagram illustrating an example of an association (or, an association candidate) between a DMRS port, a PUSCH antenna port, and a PTRS port.

[0025] Figures 11A to 11D This is a conceptual diagram representing the resource set / resource correspondence (modes 1-4) in the codebook for 3TX UE.

[0026] Figures 12A to 12C This is a conceptual diagram illustrating an example of a time-domain SRS mapping according to Embodiment 1 of the first implementation.

[0027] Figure 13A and Figure 13B This is a diagram illustrating an example of the SRI field involved in the second embodiment.

[0028] Figure 14A and Figure 14B This is a diagram illustrating an example of the PTRS-DMRS association field involved in the fourth embodiment.

[0029] Figure 15 This is a diagram illustrating a variation of the PTRS-DMRS association field according to the fourth embodiment.

[0030] Figure 16 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment.

[0031] Figure 17 This is a diagram illustrating an example of the structure of a base station according to one embodiment.

[0032] Figure 18 This is a diagram illustrating an example of the structure of a user terminal according to one embodiment.

[0033] Figure 19 This is a diagram illustrating an example of the hardware structure of a base station and a user terminal according to one embodiment.

[0034] Figure 20 This is a diagram illustrating an example of a vehicle according to one embodiment. Detailed Implementation

[0035] (Control of SRS and PUSCH transmission)

[0036] In Rel.15 NR, terminals (user terminals, user equipment (UE)) can also receive information transmitted for measurement reference signals (e.g., sounding reference signals (SRS)) (SRS configuration information, e.g., parameters in the "SRS-Config" of the RRC control element).

[0037] Specifically, the UE may also receive at least one of the following: information related to one or more SRS resource sets (SRS resource set information, such as “SRS-ResourceSet” of RRC control elements) and information related to one or more SRS resources (SRS resource information, such as “SRS-Resource” of RRC control elements).

[0038] A single SRS resource set can also be associated with a specific number of SRS resources (or grouped together). Each SRS resource can also be identified by an SRS resource identifier (SRS Resource Indicator (SRI)) or an SRS resource ID (Identifier).

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

[0040] Here, the SRS resource type can also represent any of the following: Periodic SRS (P-SRS), Semi-Persistent SRS (SP-SRS), and Aperiodic CSI (A-SRS). Additionally, the UE can periodically (or periodically after activation) send P-SRS and SP-SRS, and send A-SRS based on DCI SRS requests.

[0041] Furthermore, the usage (“usage” in the RRC parameter, “SRS-SetUse” in the L1 (Layer-1) parameter) can also be, for example, beam management, codebook (CB) or noncodebook (NCB) usage, antenna switching, etc. SRS for codebook or noncodebook usage can also be used to determine the precoder for SRI-based, codebook-based or noncodebook-based uplink shared channel (PUSCH) transmission.

[0042] For example, in codebook-based transmission, the UE can determine the precoder (precoding matrix) used for PUSCH transmission based on the SRI, the Transmitted Rank Indicator (TRI), and the Transmitted Precoding Matrix Indicator (TPMI). In non-codebook-based transmission, the UE can also determine the precoder used for PUSCH transmission based on the SRI.

[0043] SRS resource information may also include SRS resource ID (SRS-ResourceId), number of SRS ports, SRS port number, transmission comb, SRS resource mapping (e.g., time and / or frequency resource location, resource offset, resource period, number of repetitions, number of SRS symbols, SRS bandwidth, etc.), hop association information, SRS resource type, sequence ID, SRS spatial relationship information, etc.

[0044] Spatial relation information of an SRS (e.g., "spatialRelationInfo" in an RRC information element) can also represent spatial relation information between a specific reference signal and an SRS. This specific reference signal can be at least one of a Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block, a Channel State Information Reference Signal (CSI-RS) block, and an SRS (e.g., another SRS). An SS / PBCH block can also be referred to as a Synchronization Signal Block (SSB).

[0045] SRS spatial relationship information may also include at least one of the following: SSB index, CSI-RS resource ID, and SRS resource ID, as an index to the aforementioned specific reference signal.

[0046] Additionally, in this disclosure, the SSB index, SSB resource ID, and SSB resource indicator (SSB Resource Indicator (SSBRI)) can be interchanged. Furthermore, the CSI-RS index, CSI-RS resource ID, and CSI-RS resource indicator (CSI-RS Resource Indicator (CRI)) can also be interchanged. Furthermore, the SRS index, SRS resource ID, and SRI can also be interchanged.

[0047] The spatial relationship information of SRS can also include serving cell index, BWP index (BWP ID), etc., corresponding to the specific reference signal mentioned above.

[0048] Regarding a specific SRS resource, if spatial relationship information related to the SSB or CSI-RS and the SRS is configured, the UE can also use the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter (spatial domain receive filter) used for receiving the SSB or CSI-RS to transmit the SRS resource. In this case, the UE can also assume that the UE receive beam for the SSB or CSI-RS is the same as the UE transmit beam for the SRS.

[0049] Regarding a specific SRS (target SRS) resource, if spatial relationship information related to other SRSs (reference SRSs) and that SRS (target SRS) is configured, the UE can also use the same spatial domain filter (spatial domain transmission filter) as the one used for transmitting the reference SRS to transmit the target SRS resource. In other words, in this case, the UE can also assume that the UE transmission beam for the reference SRS is the same as the UE transmission beam for the target SRS.

[0050] The UE can also determine the spatial relationship of PUSCHs scheduled through the DCI based on the value of a specific field (e.g., the SRS Resource Identifier (SRI) field) within the DCI (e.g., DCI format 0_1). Specifically, the UE can also use the spatial relationship information of the SRS resources determined based on the value of that specific field (e.g., SRI) (e.g., the "spatialRelationInfo" of the RRC information element) for PUSCH transmission.

[0051] In Rel.15 / 16 NR, for PUSCH, when using codebook-based transmission, the UE can also be configured via RRC to have a set of SRS resources with a maximum of 2 SRS resources used for codebook transmission, and one of these 2 maximum SRS resources is indicated via DCI (1-bit SRI field). The PUSCH transmission beam is specified via the SRI field.

[0052] The UE can also determine the TPMI and layer number (transmission rank) used for PUSCH based on precoding information and the layer number field (hereinafter also referred to as the precoding information field). The UE can also select a precoder from the codebook for the uplink with the same number of ports as the SRS ports, based on the aforementioned TPMI, layer number, etc. The number of SRS ports is represented by the "nrofSRS-Ports" parameter set by the higher layer for the SRS resources specified by the aforementioned SRI field.

[0053] In Rel.15 / 16 NR, when using non-codebook-based transmission for PUSCH, the UE can also be configured via RRC to have a set of SRS resources with a maximum of 4 SRS resources for non-codebook purposes, and be indicated by DCI (2-bit SRI field) for one or more of these maximum 4 SRS resources.

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

[0055] When a CSI-RS (also referred to as an associated CSI-RS) is configured at a higher level to be associated with the SRS resource (or the SRS resource set to which the SRS resource belongs), the PUSCH transmit beam can also be calculated based on the measurements of the configured associated CSI-RS. Otherwise, the PUSCH transmit beam can also be specified via SRI.

[0056] Additionally, the UE can be configured to use either codebook-based PUSCH transmission or non-codebook-based PUSCH transmission via the higher-level parameter "txConfig," which represents the transmission scheme. This parameter can also represent the value of "codebook" or "non-codebook."

[0057] In this disclosure, codebook-based PUSCH (codebook-based PUSCH transmission, codebook-based transmission) can also refer to PUSCH in the case where a "codebook" is set as the transmission scheme in the UE. In this disclosure, non-codebook-based PUSCH (non-codebook-based PUSCH transmission, non-codebook-based transmission) can also refer to PUSCH in the case where a "non-codebook" is set as the transmission scheme for the UE.

[0058] (Decision of the PUSCH precoder in codebook (CB) based transmission)

[0059] As mentioned above, in the case of codebook-based (CB) transmission, the UE can also determine the precoder used for PUSCH transmission based on SRI, TRI, TPMI, etc.

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

[0061] TRI and TPMI can also be specified via the DCI precoding information and the "Precoding information and number of layers" field. For simplicity, the precoding information and the layer number field are also referred to as the precoding information field.

[0062] The UE can also report UE capability information related to the precoder type, and the precoder type can be set from the base station via higher-layer signaling based on this UE capability information. This UE capability information can also be information about the precoder type used by the UE in PUSCH transmission (for example, it can also be represented by the RRC parameter "pusch-TransCoherence").

[0063] The UE can also determine the precoder to use in PUSCH transmission based on the precoder type information (e.g., the RRC parameter "codebookSubset") contained in the PUSCH configuration information (e.g., the "PUSCH-Config" information element in RRC signaling) notified via higher-layer signaling. The UE can also be configured with a subset of the PMIs specified via TPMI through codebookSubset.

[0064] Additionally, the precoder type can also be specified by any one of fully coherent, fully coherent, partially coherent, and non-coherent, or a combination of at least two of these (e.g., it can also be represented by parameters such as "fullyAndPartialAndNonCoherent", "partialAndNonCoherent", etc.).

[0065] For example, the RRC parameter "pusch-TransCoherence" representing UE capabilities can also mean full coherent, partial coherent, or noncoherent. Furthermore, the RRC parameter "codebookSubset" can also mean "fully and partially and noncoherent," "partial and noncoherent," or "noncoherent."

[0066] Fully coherent can also mean that synchronization has been achieved across all antenna ports used for transmission (it can also be described as being able to achieve phase consistency, phase control per coherent antenna port, and appropriate pre-encoder implementation per coherent antenna port, etc.). Partially coherent can also mean that a portion of the antenna ports used for transmission are synchronized, but this portion is not synchronized with the other ports. Incoherent can also mean that synchronization has not been achieved across the antenna ports used for transmission.

[0067] Furthermore, a UE that supports fully coherent precoder types can also be envisioned as supporting partially coherent and non-coherent precoder types. A UE that supports partially coherent precoder types can also be envisioned as supporting non-coherent precoder types.

[0068] In this disclosure, precoder type, coherency, PUSCH transmission coherence, coherence type, coherence type, codebook type, codebook subset, codebook subset type, etc., can also be interchanged.

[0069] The UE can also determine, from among the multiple precoders (also referred to as precode matrices, codebooks, etc.) used for CB-based transmission, the precoder corresponding to the TPMI index that can be obtained from the DCI (e.g., DCI format 0_1, hereinafter the same) that can be used to schedule UL transmission.

[0070] Figure 1 This is a diagram illustrating an example of the association between a subset of the codebook and the TPMI index. Figure 1 This is equivalent to the table in Rel.16 NR of the precoding matrix W used for single-layer (rank 1) transmission with 4 antenna ports when transform precoding (also known as transform precoder) is invalid. Figure 1 The corresponding W (W) are shown in ascending order of the TPMI index from left to right. Figure 2 (The same applies).

[0071] like Figure 1 The representation of the correspondence between the TPMI index and the corresponding W (also known as a table) is called a codebook. A portion of this codebook is also called a codebook subset.

[0072] exist Figure 1In the case of a codebook subset that is fully, partially, and noncoherent, the UE is notified of any TPMI (TPMI index) from 0 to 27 for single-layer transmission. Furthermore, in the case of a codebook subset that is partially and noncoherent, the UE is set to any TPMI from 0 to 11 for single-layer transmission. In the case of a noncoherent codebook subset, the UE is set to any TPMI from 0 to 3 for single-layer transmission.

[0073] exist Figure 1 In the TPMI settings, incoherent precoders are applied when the notification is 0 to 3. Partially coherent precoders are applied when the notification is 4 to 11. Fully coherent precoders are applied when the notification is 12 to 27.

[0074] Figures 2 to 4 These are tables corresponding to the precoding matrices W used for 2-4 layer (rank 2-4) transmission with 4 antenna ports in Rel.16 NR when the transform precoding is invalid.

[0075] according to Figure 2 The TPMI notified to the UE for Layer 2 transmission is 0 to 21 (codebook subset is complete, partial and incoherent), 0 to 13 (codebook subset is partial and incoherent) or 0 to 5 (codebook subset is incoherent).

[0076] according to Figure 3 The TPMI notified to the UE for Layer 3 transmission is 0 to 6 (codebook subset is complete, partial and incoherent), 0 to 2 (codebook subset is partial and incoherent) or 0 (codebook subset is incoherent).

[0077] according to Figure 4 The TPMI notified to the UE for Layer 4 transmission is 0 to 4 (codebook subset is complete, partial and incoherent), 0 to 2 (codebook subset is partial and incoherent) or 0 (codebook subset is incoherent).

[0078] Figure 5A This is equivalent to the table of the precoding matrix W used for single-layer (rank 1) transmission with two antenna ports in Rel.16 NR. Figure 5B This is equivalent to the table in Rel.16 NR that uses the precoding matrix W for two-layer (rank 2) transmission with two antenna ports in the case of invalid transformation precoding.

[0079] according to Figure 5A For single-layer transmission on port 2, the UE is notified of a TPMI of 0 to 5 (codebook subset includes full, partial, and incoherent components) or 0 to 1 (codebook subset includes incoherent components). When the notified TPMI is 0 to 1, an incoherent precoder is applied. When the notified TPMI is 2 to 5, a fully coherent precoder is applied.

[0080] according to Figure 5B The TPMI notified to the UE for the 2-port 2-layer transmission is 0 to 2 (codebook subset is complete, partial and incoherent) or 0 (codebook subset is incoherent).

[0081] Furthermore, a precoding matrix in which only one element in each column is non-zero can also be called an incoherent codebook. A precoding matrix in which only a specific number of elements (greater than 1, but not the total number of elements in the column) in each column are non-zero can also be called a partially coherent codebook. A precoding matrix in which all elements in each column are non-zero can also be called a fully coherent codebook.

[0082] Incoherent codebooks and partially coherent codebooks can also be referred to as antenna selection precoders, antenna port selection precoders, etc. For example, an incoherent codebook (non-phase interference encoder) can also be referred to as a 1-port selection precoder, a 1-port port selection precoder, etc. Furthermore, a partially coherent codebook (partial phase interference encoder) can also be referred to as an x-port (x is an integer greater than 1) selection precoder, an x-port port selection precoder, etc. A fully coherent codebook can also be referred to as a non-antenna selection precoder, a full-port precoder, etc. In this disclosure, codebook, codebook subset, and precoder can also be used interchangeably.

[0083] Additionally, in this disclosure, a partially coherent codebook can also be equivalent to: a codebook from the codebook (precoding matrix) corresponding to the TPMI specified by DCI for codebook-based transmission for UEs with a partially coherent codebook subset (e.g., RRC parameter "codebookSubset" = "partialAndNonCoherent"), after removing the codebook corresponding to the TPMI specified for UEs with a non-coherent codebook subset (e.g., RRC parameter "codebookSubset" = "nonCoherent") (that is, for single-layer transmission with 4 antenna ports, it is a codebook with TPMI = 4 to 11).

[0084] Additionally, in this disclosure, a fully coherent codebook can also be equivalent to: a codebook (precoding matrix) from which the TPMI corresponding to the UE specified by the DCI for codebook transmission based on a fully coherent codebook subset (e.g., RRC parameter "codebookSubset" = "fullyAndPartialAndNonCoherent") is removed, after removing the codebook corresponding to the TPMI specified by the UE for codebook transmission based on a partially coherent codebook subset (e.g., RRC parameter "codebookSubset" = "partialAndNonCoherent"). (That is, for single-layer transmission with 4 antenna ports, it is a codebook with TPMI = 12 to 27.)

[0085] In addition, by Figure 5A and Figure 5B It is known that since there is no partial phase interference encoder for transmission at the two antenna ports, the settings that the codebook subset is partial and incoherent for the two antenna ports can also be disregarded.

[0086] (Pre-encoded information field)

[0087] As mentioned above, the UE can also determine the TPMI and layer number (transmission rank) used for the PUSCH based on the precoding information field of the DCI (e.g., DCI format 0_1 / 0_2) of the PUSCH.

[0088] Regarding codebook-based PUSCH, the number of bits in the precoding information field can also be determined (and can be varied) based on settings such as the validity of the transform precoder used for PUSCH (e.g., the higher-layer parameter transformPrecoder), the setting of the codebook subset used for PUSCH (e.g., the higher-layer parameter codebookSubset), the setting of the maximum number of layers used for PUSCH (e.g., the higher-layer parameter maxRank), the setting of uplink full-power transmission used for PUSCH (e.g., the higher-layer parameter ul-FullPowerTransmission), and the number of antenna ports used for PUSCH.

[0089] Figure 6This diagram illustrates an example of the correspondence between the field values ​​of precoding information and layer number in Rel.16 NR, and the layer number and TPMI. This example shows the correspondence for four antenna ports when the transform precoder is set to invalid, the maximum rank (maxRank) is set to 2, 3, or 4, and uplink full-power transmission is not set, or is set to full-power mode 2, or is set to full power, but is not limited to this. Furthermore, those skilled in the art will naturally understand that the "bit field mapped to index" in the diagram represents the field values ​​of precoding information and layer number.

[0090] exist Figure 6 In the UE, the precoding information field is 6 bits when the codebook subset is set to fully coherent (fully And Partial And Non Coherent), 5 bits when the codebook subset is set to partially coherent (partial And Non Coherent), and 4 bits when the codebook subset is set to non Coherent (non Coherent).

[0091] In addition, such as Figure 6 As shown, the layer number and TPMI corresponding to the value of a certain precoding information field can also be the same (common) regardless of the codebook subset set in the UE. For example, in Figure 6 In this context, the precoding information field value (0-11) represents the layer number and TPMI, which can also be the same for fully coherent (fully And Partial And Non-Coherent), partially coherent (partial And Non-Coherent), and non-coherent codebook subsets. Furthermore, in... Figure 6 In this context, the value of the precoding information field, 0-31, represents the layer number and TPMI, which can also be the same for fully coherent (fully And Partial And Non Coherent) and partially coherent (partial And Non Coherent) codebook subsets.

[0092] Alternatively, the precoding information field can also be 0 bits with respect to a non-codebook-based PUSCH. Furthermore, the precoding information field can also be 0 bits with respect to a codebook-based PUSCH for one antenna port.

[0093] (SRS settings for PUSCH based on the codebook)

[0094] Figure 7AThis means that in Rel.17, ul-FullPowerTransmission is not set, or ul-FullPowerTransmission=fullpowerMode1, or ul-FullPowerTransmission=fullpowerMode2, or ul-FullPowerTransmission=fullpower and N SRS A diagram showing the SRI indication or second SRI indication during codebook-based PUSCH transmission when the value is 2. Figure 7B This refers to Rel.17, where ul-FullPowerTransmission=fullpowerMode2 and N SRS A diagram of SRI indication or second SRI indication for codebook-based PUSCH transmission when =3. Figure 7C This refers to Rel.17, where ul-FullPowerTransmission=fullpowerMode2 and N SRS When =4, a diagram for SRI indication or second SRI indication used for codebook-based PUSCH transmission.

[0095] 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. When txConfig=nonCodeBook, is set via srs-ResourceSetToAddModList, and there are two SRS resource sets associated with the purpose of "nonCodeBook"; or when txConfig=codebook, is set via srs-ResourceSetToAddModList, and there are two SRS resource sets associated with the purpose of "codebook", the SRS Resource Set Indicator field becomes 2 bits. Otherwise, the SRS Resource Set Indicator field becomes 0 bits.

[0096] When the high-level parameter txConfig=codebook is used, follow Figures 7A to 7C The SRS Resource Indicator field is [log2(NSRS )] bits. N SRS This is the number of SRS resources set within the SRS resource set, indicated by the SRS resource set indicator field (if present). Otherwise, N SRS It is the number of SRS resources set within the SRS resource set configured via the high-level parameter srs-ResourceSetToAddModList and associated with the usage of the high-level parameter 'codeBook'.

[0097] In codebook-based transmission, PUSCH is scheduled via DCI format 0_0, DCI format 0_1, and DCI format 0_2, or configured semi-fixedly. Only one or two SRS resource sets can be set in the SRS-ResourceSetToAddModList of the "codebook" purpose, which has higher-level parameters for SRS-ResourceSet. Furthermore, only one or two SRS resource sets can be set in the srs-ResourceSetToAddModListDCI-0-2 of the "codebook" purpose, which has higher-level parameters for SRS-ResourceSet.

[0098] In srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, when the purpose of the high-level parameter of SRS-ResourceSet is set to "codebook" and two SRS resource sets are set, one or two SRIs and one or two TPMIs are given through two SRS resource indicator fields and two precoding information fields respectively.

[0099] The UE follows the SRS resource set associated with PUSCH repetitions, applying the indicated SRI(s) and TPMI(s) to more than one PUSCH repetition. When two SRS resource sets are configured via SRS-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, and the purpose of the higher-level parameters of SRS-ResourceSet is set to "codebook", the UE may not expect different numbers of SRS resources to be configured in the two SRS resource sets.

[0100] In codebook-based transmission, only one SRS resource may be indicated from the SRS resource set based on SRI. Except when the higher-layer parameter "ul-FullPowerTransmission" is set to "fullpowerMode2", the maximum number of SRS resources configured for codebook-based transmission is two. When aperiodic SRS is configured for the UE, the SRS request field of the DCI triggers the transmission of aperiodic SRS resources.

[0101] Except when the higher-level parameter “ul-FullPowerTransmission” is set to “fullpowerMode2”, when multiple SRS resources are set to “codebook” through SRS-ResourceSet, the UE expects the higher-level parameter “nrofSRS-Port” of SRS-Resource in SRS-ResourceSet to be set to the same value for all SRS resources.

[0102] When the high-level parameter “ul-FullPowerTransmission” is set to “fullpowerMode2”, the following (1) to (3) are applied.

[0103] (1) Within an SRS resource set whose purpose is set as “codebook”, the UE can set one SRS resource or multiple SRS resources with the same or different number of SRS ports.

[0104] (2) When multiple SRS resources are set in an SRS resource set, a maximum of two different spatial relationships can be set for all SRS resources in the SRS resource set whose purpose is set as "codebook".

[0105] (3) Depending on the UE’s capabilities, a maximum of two or four SRS resources are supported within an SRS resource set whose purpose is set to “codebook”.

[0106] In the typical codebook-based PUSCH scenario, a single SRS resource set with two SRS resources having the same number of ports can be configured. In the case of repeated codebook-based PUSCH (used for multiple transmission / reception points (TRPs)), two SRS resource sets with the same number of SRS resources can also be configured separately. In the "fullpowerMode2" codebook-based configuration, a single SRS resource set with the same or different numbers of ports can be configured.

[0107] (Transmission from more than 4 antenna ports)

[0108] In Rel.15 / 16 NR, up to four layers of uplink (UL) multi-input multi-output (MIMO) transmission are supported. For future wireless communication systems, to achieve higher spectral efficiency, support for UL transmission with more than four layers is under investigation. 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 investigated.

[0109] Figure 8 This diagram illustrates an example of an antenna layout with 8 antenna ports. Ng represents the number of antenna groups. M represents the number of antennas (or antenna elements) in the first dimension, and N represents the number of antennas (or antenna elements) in the second dimension. The first and second dimensions can be, for example, the horizontal and vertical directions. P represents the number of polarization surfaces. When P=2, it is called an interleaved polarization antenna.

[0110] Antenna groups can also be called coherent groups. A coherent group can contain more than one coherent port. For example, a partially coherent UE can also have multiple coherent groups. Antenna ports within a coherent group can also be coherent. Antenna ports between different coherent groups can also be incoherent.

[0111] Each coherent group can also correspond to a different transmit panel / transmit chain (Tx chain) / SRS resource set / RS resource set / spatial relation info / joint transmission configuration indication state (joint TCI state) / UL TCI state / receive TRP. Here, the SRS resource set can also specifically be equivalent to an SRS resource set used as a codebook or not. Furthermore, each coherent group can also correspond to other receive TRPs. Additionally, coherent groups can also be referred to as coherent antenna groups, port groups, antenna sets, etc.

[0112] The UE can also report the supported antenna groups / antenna configuration information / coherence count as UE capability information. In addition, the UE can also have coherence groups configured via higher-layer signaling (e.g., the number of coherence groups and the number of ports contained in each coherence group).

[0113] In addition, antenna layout is not affected Figure 8The examples shown are limited. For example, the number of antenna panels, the orientation of the panels, the coherence of each panel / antenna (fully coherent, partially coherent, incoherent, etc.), the specific orientation of the antenna array (horizontal, vertical, etc.), and the polarization antenna structure (single polarization, interleaved polarization, number of polarization surfaces, etc.) can also be related to... Figure 7A and Figure 7B The examples are different. dG-H and dG-V represent the horizontal and vertical spacing between the centers of adjacent antenna groups, respectively.

[0114] Furthermore, while the transmission of one codeword (CW) within a PUSCH is supported in Rel.15 / 16 NR, the transmission of more than one CW within a PUSCH by the UE is under investigation for Rel.18 NR. For example, support for 2CW transmission for rank 5-8 and 2CW transmission for rank 2-8 are being investigated.

[0115] Furthermore, in Rel.15 and Rel.16 UEs, it was envisioned that only one beam / panel would be used for UL transmission at any given time. However, in Rel.17 and later, to improve UL throughput and reliability, simultaneous UL transmission (e.g., PUSCH transmission) of multiple beams / panels is being studied for TRPs of 1 or higher. Additionally, simultaneous PUSCH transmission of multiple beams / panels can be equivalent to PUSCH transmission with more than 4 layers, or it can be equivalent to PUSCH transmission with fewer than 4 layers.

[0116] Furthermore, precoding matrices for UL transmission using more than 4 antenna ports are being investigated. For example, codebooks for 8-port transmission are being studied (also known as 8-transmission UL codebook TX UL codebook, etc.).

[0117] (SRS resource settings for codebook-based PUSCH transmission)

[0118] For example, in a single TRP transmission in Rel.18, one SRS resource set can be configured with its usage set to the codebook. Except for full-power mode 2, two SRS resources can be configured within this SRS resource set (each SRS resource set).

[0119] In multi-TRP transmission, two SRS resource sets can be configured with usage set to the codebook. Except for full-power mode 2, two SRS resources can be configured in each SRS resource set (each SRS resource).

[0120] When multiple SRS resources are set for (1) SRS resource set, the precoder for codebook-based transmission corresponds to the SRS resource selected via the SRI field.

[0121] When a single SRS resource is set for a (1) SRS resource set (excluding the SRI field), the precoder for codebook-based transmission corresponds to that SRS resource.

[0122] In a single TRP transmission, one SRI field is indicated within the DCI. In a multi-TRP transmission, two SRI fields are indicated within the DCI.

[0123] Here, the number of bits in the SRI field is determined by ceil(log2(N)). SRS ) indicates. N SRS It is the number of SRS resources contained within the SRS resource set. Additionally, in this disclosure, ceil(X) can also refer to applying a floor function to X.

[0124] For example, suppose in DCI format 0_2, N is set for one SRS resource set. SRS，0_2 For each SRS resource, the SRS resource set for DCI format 0_2 can also be set (including) the initial N of the SRS resource set set for DCI format 0_1. SRS，0_2 One SRS resource.

[0125] As for the existing specifications, a table of SRI instructions for codebook-based PUSCH transmissions can be referenced, for example, as described above. Figure 7A .exist Figure 7A The diagram illustrates the cases where UL full power transmission is not set (ul-FullPowerTransmission), the cases where full power mode 2 is set (ul-FullPowerTransmission = fullpowerMode2), and the cases where UL full power transmission is set (ul-FullPowerTransmission = fullpower) and N SRS =2.

[0126] Furthermore, in Rel.19 and later, there may be cases where the aforementioned uplink (UL) full-power transmission is not supported and is not accompanied by SRS enhancement / extension. In such cases, in order to easily implement codebook-based transmission using 3 antenna ports, the specification of an incoherent UL codebook (an incoherent codebook for UL) is being studied.

[0127] Research is underway on new codebooks for 3TX UEs. In new codebook-based PUSCHs for 3TX UEs (e.g., including Set Grant (CG) PUSCH and Dynamic Grant (DG) PUSCH), a maximum of two (i.e., one or two) SRS resources (using SRS resources with three antenna ports) can be set for one SRS resource set.

[0128] For example, SRS using 3 antenna ports (also known as 3-port SRS) is not supported in existing specifications, nor is enhancement / extension of this SRS supported. Therefore, for codebook-based Layer 3 transmission (3Tx for usage='codebook'), the SRS settings shown in the following options can also be considered. That is, the UE can control SRS transmission by following at least one of the following options.

[0129] [Option 1]

[0130] A maximum of two (i.e., one or two) SRS resources can be configured for one SRS resource set (SRS resources using four antenna ports). Here, which three of the four antenna ports are actually used and correspond to the antenna ports used for TPMI indication can be defined in advance by the specification (e.g., antenna ports 0~2 of SRS correspond to antenna ports 0~2 of TPMI (TPMI=0~2)) or can be set in the SRS settings.

[0131] In this case, even if, for example, SRS is configured to use 4 antenna ports, the UE will use 3TX (3 SRS antenna ports 0~2) to transmit SRS for that configuration (4-port SRS configuration).

[0132] That is, in this case, even if the SRS is configured to use 4 antenna ports, the UE can assume that it is configured to use 3 antenna ports and control the transmission of SRS (PUSCH).

[0133] [Option 2]

[0134] A 3-port SRS resource (an SRS resource using 3 antenna ports) can refer to one 1-port SRS (an SRS corresponding to 1 antenna port) and two other 2-port SRSs (SRSs corresponding to 2 antenna ports). Here, the correspondence between the 3 ports (3 antenna ports) and the TPMI indication can be predefined by the specification (e.g., TPMI antenna port 0 corresponds to a 1-port SRS, TPMI antenna ports 1 and 2 correspond to 2-port SRS, or TPMI antenna ports 0 and 1 correspond to 2-port SRS, and TPMI antenna port 2 corresponds to a 1-port SRS), configured in the SRS settings, or dynamically indicated by a new field within the DCI.

[0135] [Option 3]

[0136] A 3-port SRS resource (an SRS resource using 3 antenna ports) can also refer to 3 1-port SRSs (SRSs corresponding to 1 antenna port). Here, the correspondence between the 3 ports (3 antenna ports) and the TPMI indication can be predefined by the specification (e.g., TPMI antenna port 0 corresponds to the first 1-port SRS, TPMI antenna port 1 corresponds to the second 1-port SRS, and TPMI antenna port 2 corresponds to the third 1-port SRS), configured in the SRS settings, or dynamically indicated through a new field within the DCI.

[0137] (PTRS)

[0138] In Rel.15 NR, Phase Tracking Reference Signal (PTRS) is supported. Base stations can also transmit PTRS via the downlink. Base stations can also map and transmit PTRS continuously or discontinuously in the time direction across a specific number (e.g., 1) of subcarriers.

[0139] The UE may also receive PTRS during at least a portion of the period (time slot, symbol, etc.) during which the downlink shared channel (Physical Downlink Shared Channel (PDSCH)) is scheduled (in other words, the period for receiving the PDSCH). The PTRS transmitted by the base station may also be referred to as DL PTRS.

[0140] In addition, the UE can also transmit PTRS via the uplink. The UE can also map and transmit PTRS continuously or discontinuously in the time direction on a specific number (e.g., 1) of subcarriers.

[0141] The UE may also transmit PTRS during at least a portion of the period (time slot, symbol, etc.) during which the uplink shared channel (PUSCH) is scheduled (in other words, the period during which PUSCH is transmitted). The PTRS transmitted by the UE may also be referred to as UL PTRS.

[0142] The base station or UE can also determine the phase noise based on the received PTRS and correct the phase error of the received signal (e.g., PUSCH, PDSCH).

[0143] The UE can also use higher-layer signaling to configure PTRS configuration information (PTRS-DownlinkConfig for DL, PTRS-UplinkConfig for UL). For example, this PTRS configuration information can also be included in the configuration information (DMRS-DownlinkConfig, DMRS-UplinkConfig) of the demodulation reference signal (DMRS) of the PDSCH or PUSCH.

[0144] (PTRS and DMRS)

[0145] In NR (e.g., Rel. 15), it is envisioned that a DMRS port associated with a PTRS port is a QCL with respect to QCL types A and D. In other words, it can also be envisioned that when a PTRS port is associated with a DMRS port, the PTRS port and the DMRS port are in a relationship of QCL types A and D with each other.

[0146] In Rel.16 NR, support for associations between PTRS and DMRS ports (e.g., PTRS-DMRS association) is indicated by a specific field in the DCI. This specific field may also be referred to as the PTRS-DMRS association field or the PTRS-DMRS association field (e.g., the PTRS-DMRS association field).

[0147] In Rel.16 NR, the following protocol was established: For multi-panel / TRP transmission based on a single PDCCH, a maximum of two PTRS ports (a first PTRS port and a second PTRS port) are supported. The number of PTRS ports applied / configured (e.g., 1 or 2 PTRS ports) can also be notified to the UE via higher-layer parameters.

[0148] When only one PTRS port is configured (e.g., PTRS port #0), the association between PTRS and DMRS can also be determined based on the code points specified through the PTRS-DMRS association field of the DCI, and the correspondence between each code point and the DMRS port (e.g., a table). The correspondence between each code point and the DMRS port (e.g., a table) can also be predefined (see [link to documentation]). Figure 9A ).

[0149] exist Figure 9A The diagram shows how each code point (0~3) in the PTRS-DMRS association field corresponds to a specific DMRS port (here, the 1st to 4th scheduled DMRS ports respectively).

[0150] When two PTRS ports are configured (e.g., PTRS port #0 and PTRS port #1), the association between each PTRS and DMRS can also be determined based on the code points specified through the PTRS-DMRS association field of the DCI, and the correspondence between each code point and the DMRS port (e.g., a table). The correspondence between each code point and the DMRS port (e.g., a table) can also be predefined (see [link to documentation]). Figure 9B ).

[0151] For example, a portion of the code points (e.g., the most significant bit (MSB)) can be used to designate the DMRS port for PTRS port #0, and the remaining code points (e.g., the least significant bit (LSB)) can be used to designate the DMRS port for PTRS port #1.

[0152] exist Figure 9B The diagram illustrates the designation of the first DMRS in the shared PTRS#0 DMRS when the MSB (here, 1 bit) is 0, and the designation of the second DMRS in the shared PTRS#0 DMRS when the MSB is 1. Furthermore, it illustrates the designation of the first DMRS in the shared PTRS#1 DMRS when the LSB (here, 1 bit) is 0, and the designation of the second DMRS in the shared PTRS#1 DMRS when the LSB is 1.

[0153] Information related to the DMRS (e.g., the first DMRS / second DMRS) sharing each PTRS (here, PTRS #0, #1) can be specified in advance through the specification, or can be explicitly or implicitly notified to the UE from the base station via DCI / RRC.

[0154] For example, the PUSCH antenna port corresponding to each PTRS port can be predefined / set, and specific information related to the correspondence between the PUSCH antenna port and the DMRS port can be notified to the UE via DCI / RRC. The UE can also determine the association between the DMRS port and the PTRS port based on the information related to the correspondence between the DMRS port and the PUSCH antenna port notified from the base station, and the predefined correspondence between the PUSCH antenna port and the PTRS port.

[0155] Specific information related to the correspondence between PUSCH antenna ports and DMRS ports can also be indicated to the UE through specific fields contained in the DCI (e.g., the DCI used in PUSCH scheduling). The specific field can also be at least one of the precoding information and layer number field, and the antenna port field.

[0156] For example, it can also be defined as follows: PUSCH antenna ports 1000 and 1002 in the indicated Transmitted Precoding Matrix Indicator (TPMI) share PTRS port #0, and PUSCH antenna ports 1001 and 1003 in the indicated TPMI share PTRS port #1. The TPMI can also be specified via the DCI's precoding information and the "Precoding information and number of layers" field (see [link to DCI documentation]). Figure 10 ).

[0157] PTRS port #0 can also be associated with UL layer 'x' of multiple layers transmitted via PUSCH antenna ports 1000 and 1002 in the indicated TPMI. PTRS port #1 can also be associated with UL layer 'y' of multiple layers transmitted via PUSCH antenna ports 1001 and 1003 in the indicated TPMI. x / y can also be associated via the PTRS-DMRS association field included in the DCI (e.g., Figure 9B (and was given.)

[0158] Alternatively, it can be defined by specification: PUSCH antenna ports 1000 and 1002 share PTRS port #0, and PUSCH antenna ports 1001 and 1003 share PTRS port #1. Specific information from the base station (hereinafter simply referred to as "TPMI") indicates which layer / DMRS port is transmitted through which PUSCH antenna port. This means that TPMI indicates which layer / DMRS port shares which PTRS port. Alternatively, the PTRS-DMRS association field can be used to indicate that one of multiple layer / DMRS ports shares a PTRS port.

[0159] (SRS transmit power control)

[0160] Using index l of the power control adjustment state (closed-loop state), the SRS transmission power (P) in the SRS transmission opportunity (transmission occasion) (also known as transmission period, etc.) i of the active UL BWP b of carrier f for serving cell c is... SRS、b，f，c (i, q) s ,l)) based on P CMAX，f，c (i) P O_SRS，b，f，c (q) s M SRS，b，f，c (i) α SRS，b，f，c (q) s ), PL b，f，c (q) d h b，f，c (i, l) is given by the following formula.

[0161]

[0162] In addition, SRS transmission opportunity i is the period during which SRS is transmitted, and for example, it can also consist of more than one symbol, more than one time slot, etc.

[0163] Here, P CMAX，f，c (i) For example, the maximum output power of the UE used for carrier f of serving cell c in SRS transmission opportunity i. O_SRS，b，f，c (q) s ) is achieved through the activation of the UL BWP b on carrier f for serving cell c, and the SRS resource set q. s The parameters related to the target received power provided by p0 (provided via SRS-ResourceSet and SRS-ResourceSetId) (e.g., also referred to as parameters related to transmit power offset, transmit power offset P0, or target received power parameters, etc.).

[0164] M SRS，b，f，c (i) is the SRS bandwidth represented by the number of resource blocks on the active UL BWP b for SRS transmission opportunity i for the serving cell c and the carrier f with subcarrier spacing μ.

[0165] α SRS，b，f，c (q) s By activating the UL BWP b for the serving cell c and the carrier f with subcarrier spacing μ, and the SRS resource set q s α (e.g., alpha) is provided.

[0166] PL b，f，c (q) d This refers to the activation DL BWP for serving cell c, and the SRS resource set q. s The UE uses the RS resource index q d Calculated DL path loss estimate [dB] (path loss estimate [dB], path loss compensation). RS resource index q d It is related to SRS resource set q s The associated path loss reference RS (path loss reference RS, path loss (PL))-RS, path loss measurement DL-RS, for example, provided by pathlossReferenceRS) is either an SS / PBCH block index (e.g., ssb-Index) or a CSI-RS resource index (e.g., csi-RS-Index).

[0167] If the UE is not given path loss reference RSs, or before the UE is given dedicated higher-layer parameters, the UE uses RS resources obtained from the SS / PBCH block used by the UE to obtain the MIB to calculate PL. b，f，c (q) d ).

[0168] h b，f，c (i, l) represents the SRS power control adjustment state for the active UL BWP of carrier f in serving cell c during SRS transmission opportunity i. If the SRS power control adjustment state setting (e.g., srs-PowerControlAdjustmentStates) represents the same power control adjustment state for both SRS transmission and PUSCH transmission, then it represents the current PUSCH power control adjustment state f. b，f，c (i, l). On the other hand, when the SRS power control adjustment state is set to represent an independent power control adjustment state for SRS transmission and PUSCH transmission, the SRS power control adjustment state h b，f，c(i) can also be based on δ SRS，b，f，c (m).

[0169] If TPC accumulation is valid, h b，f，c (i) can also be based on δ SRS，b，f，c The cumulative value of (m).

[0170] In the case where TPC accumulation is invalid, h b，f，c (i) can also be δ SRS，b，f，c (i) (absolute value).

[0171] Here, δ SRS，b，f，c (m) can also be a TPC command value encoded within a PDCCH that has DCI (e.g., DCI format 2_3) in combination with other TPC commands. Σ m=0 C（Si）-1 δ SRS，b，f，c (m) can also be on the active UL BWP b of the serving cell c and the carrier f of the subcarrier spacing μ, at SRS transmission opportunities i-i0. SRS (i-i0)-1 symbol preceding the K of SRS transmission opportunity i SRS (i) The concentration (cardinality) C(S) received by the UE between these two before the symbol i The set S of TPC command values i The total of TPC commands within. Here, i0 can also be K that enables SRS to send opportunities i-i0. SRS (i-i0)-1 symbol earlier than SRS transmission opportunity i of K SRS (i) The smallest positive integer preceding the symbol.

[0172] If the SRS transmission is aperiodic, K SRS (i) can also be the number of symbols in the active UL BWP b of carrier f of serving cell c, after the last symbol of the corresponding PDCCH that triggered the SRS transmission and before the first symbol of the SRS transmission. If the SRS transmission is semi-persistent or periodic, K SRS (i) could also be the number of symbols N in each time slot of the active UL BWP b of the carrier f of the serving cell c. symb slot K is equal to the product of the minimum value of k2 provided through the PUSCH common structure information (PUSCH-ConfigCommon). SRS，min The number of code elements.

[0173] In Rel.15 / 16, P0 and α for a closed-loop (CL) state index are set via RRC.

[0174] In Rel.17, when a TCI-State is provided within a dl-OrJointTCI-StateList or TCI-UL-State, P0 and α for a single closed-loop (CL) state index follow the following conditions:

[0175] - When followUnifiedTCIstateSRS (the setting that SRS follows the unified TCI state) is provided, it is given by p0AlphaSetforSRS associated with the indicated TCI-State or the indicated TCI-UL-State.

[0176] - Otherwise, if followUnifiedTCIstateSRS is not provided, it is given by p0AlphaSetforSRS which is associated with the TCI-State or TCI-UL-State of the SRS resource in the SRS resource set that has the lowest SRS-ResourceId.

[0177] In Rel.15 / 16, PL-RS connects with the SRS resource set q s The associated pathlossReferenceRS is provided. If no pathlossReferenceRS is provided, the UE will use RS resources obtained from the SS / PBCH block with the same SS / PBCH block index as the SS / PBCH block used to obtain the MIB for path loss calculation (as the RS resource index q used for path loss PL). d (To be used, as PL-RS). If neither pathlossReferenceRS nor spatialRelationInfo is provided, and enableDefaultBeamPL-ForSRS is set, the UE will use the default RS for path loss calculation (as the RS resource index q used for path loss PL). d (To be used as a PL-RS). The index of the default RS provides a periodic RS resource with a set qcl-Type, which is set to 'typeD' in the following TCI states or QCL assumptions:

[0178] - In the case where a CORESET is provided within the active DL BWP of serving cell c, the active DL BWP is accompanied by the TCI state or QCL assumption of the lowest indexed CORESET.

[0179] - In the case where no CORESET is provided within the active DL BWP of the serving cell c, the active PDSCH TCI state is accompanied by the lowest ID within that active DL BWP.

[0180] In Rel.17, if a TCI-State is provided within dl-OrJointTCI-StateList (a list of DL or joint TCI states) or TCI-UL-State (UL TCI states), PL-RS follows the following conditions:

[0181] - When followUnifiedTCIstateSRS is provided, it is the TCI-State that is set or the indicated TCI-State or indicated TCI-UL-State from the set of indicated TCI-UL-States, and the TCI state that is applied.

[0182] - Otherwise, the same RS as PL-RS in Rel.15 / 16 above.

[0183] Maximum transmission power (P) CMAX ))

[0184] Maximum transmit power P CMAX It is specified separately for cases involving FR1, FR2, or interoperability (e.g., EN-DC). CMAX For example, it is applied in single-carrier, CA, and DC scenarios. For instance, in the single-carrier case of FR1, P... CMAX It is specified as follows.

[0185]

[0186] UE uses equation (2) above to calculate P CMAX And it sends (reports) to the base station (gNB) using PHR MAC CE. Thus, the base station can understand the P determined by the UE. CMAX .

[0187] The following is an explanation of each parameter.

[0188] P EMAX It is given by the additionalPmax or p-Max information element in the RRC information element NR-NS-PmaxList (set by the base station).

[0189] P PowerClass This is the maximum power of the UE specified in the specification, without considering the allowable error specified in the specification. This parameter is determined by the UE and is known to the base station.

[0190] ΔP PowerClass This parameter represents the power adjustment of a high-output UE based on specific conditions. This parameter is determined by the UE and is known to the base station if the UE supports PC3.

[0191] ΔT IB，c This is an additional allowed value for serving cell c in NR Carrier Aggregation (CA), Supplemental Uplink (SUL), and E-UTRA-NR Dual Connectivity (EN-DC). This parameter is defined in the specification.

[0192] MPR stands for Maximum Power Reduction, which is used to limit the UL transmit power.

[0193] A-MPR stands for Additional Maximum Power Reduction, used to limit UL transmit power. The sum of the maximum power reductions is called the maximum (max(MPR, A-MPR)).

[0194] ΔMPR: Represents the change in MPR.

[0195] ΔT RxSRS : This is a parameter that is applied during SRS transmission when the SRS-ResourceSet is used for 'antennaSwitching'.

[0196] P-MPR stands for Power Management Maximum Power Reduction. This parameter refers to the strict adherence to electromagnetic energy absorption requirements in scenarios outside the 3GPP RAN specifications, where simultaneous transmission occurs across multiple radio access technologies (RATs), and is used to address unwanted radiated / self-sensing requirements. Furthermore, this parameter is used to ensure strict adherence to electromagnetic energy absorption requirements when proximity detection is employed to meet the need for lower maximum output power.

[0197] (Analysis 1)

[0198] According to the codebook for 3TX UEs described above, one SRS resource set may contain one 1-port SRS resource and one 2-port SRS resource (e.g., as one 3-port SRS resource), or two 1-port SRS resources and two 2-port SRS resources (e.g., as two 3-port SRS resources). In this case, one 3Tx PUSCH transmission precoder corresponds to one 1-port SRS resource and one 2-port SRS resource (Case 1).

[0199] Furthermore, as another example, an SRS resource set may contain three 1-port SRS resources (e.g., as one 3-port SRS resource) or six 1-port SRS resources (e.g., as two 3-port SRS resources). In this case, one 3TxPUSCH transmission precoder corresponds to three 1-port SRS resources (Case 2).

[0200] Furthermore, in the case of a 3Tx PUSCH transmission (3-port PUSCH transmission) precoder that is equivalent to Case 1 or Case 2 above, the limitations / constraints / regulations of the time domain resources for SRS resources are unclear (Topic 1).

[0201] Furthermore, there is room for further improvement regarding the SRI directives after Rel.19 (Topic 2).

[0202] In addition, regarding 3Tx PUSCH transmission, the association between the PTRS port and the DMRS port mentioned above needs to be specified (Project 3).

[0203] For example, if only one PTRS port is configured, consider applying the existing association between the PTRS port and the DMRS port (PTRS-DMRS association). In this case, no functional extensions for 3Tx PUSCH transmission are required.

[0204] On the other hand, even with two PTRS ports configured, functional expansion is required for the following reasons, even if the existing association between the PTRS and DMRS ports is applied.

[0205] When applying existing associations for 3Tx PUSCH transmission, PUSCH antenna ports 1000 and 1002 in the indicated TPMI share PTRS port #0, and PUSCH antenna port 1001 in the indicated TPMI uses PTRS port #1.

[0206] Based on the existing relationships mentioned above ( Figure 9B(Table), MSB indicates the DMRS port that shares PTRS port #0 (the DMRS port associated with PUSCH antenna ports 1000 and 1002), LSB indicates the DMRS port that shares PTRS port #1 (the DMRS port associated with PUSCH antenna ports 1001 and 1003).

[0207] In 3Tx PUSCH transmissions after Rel.19, since the non-phase interference encoder is considered (PUSCH antenna port 1003 is not considered), PTRS port #1 is associated with only one DMRS port and is not shared. That is to say, the LSB is actually not used.

[0208] For these reasons, it will take considerable effort to apply the existing association between PTRS and DMRS ports to 3Tx PUSCH transmission.

[0209] (Analysis 2)

[0210] As mentioned above, in 3Tx UL transmission, non-phase interference encoders are the primary consideration. Furthermore, in SRS resource settings, for an SRS resource set that can be configured, 4-port SRS resources, {1,2}-port SRS resources, {1,1,1}-port SRS resources, etc., can be considered.

[0211] In situations where multiple SRS resources are needed for such port measurements (probing), multiple SRS resources may be used in FDM (Frequency Division Multiplexed) or TDM (Time Division Multiplexed).

[0212] Furthermore, regarding SRS transmit power control, the specification describes it as follows. Additionally, matters described in the specification are equivalent to matters performed by the terminal. Furthermore, in the following description, P... – This indicates that an overline has been assigned to P, and it can also be called a P bar.

[0213] When the UE is provided with TDM for one 8-port SRS resource within one SRS resource set whose purpose is set as "codebook" or "antennaSwitching", in the active UL BWPb of carrier f in serving cell c, the UE equally divides the transmit power P among the antenna ports(s) set in each symbol used for SRS transmission. SRS，b，f，c (i, q) S The linear value P of l) -SRS，b，f，c (i, q) S ,l).

[0214] Otherwise, in the active UL BWPb of carrier f in serving cell c, the UE equally divides the transmit power P among the (multiple) antenna ports configured for SRS. SRS，b，f，c (i, q) S The linear value P of l) - SRS，b，f，c (i, q) S ,l).

[0215] In other words, according to the above-mentioned specification, the UE controls the division of transmit power among multiple antenna ports according to the following rules 1 to 2 based on the number of ports of the SRS resource.

[0216] (Rule 1)

[0217] For the 8-port SRS resource under TDM, the transmit power P SRS，b，f，c (i, q) S The linear value P of l) - SRS，b，f，c (i, q) S ,l) The (multiple) antenna ports set in each symbol transmitted by SRS are equally divided.

[0218] (Rule 2)

[0219] For other SRS resources, the transmit power P SRS，b，f，c (i, q) S The linear value P of l) - SRS，b，f，c (i, q) S ,l) are equally divided among the (multiple) antenna ports configured for SRS.

[0220] <Topic 4>

[0221] If the above rules are applied directly to a 3TX UE, the following problem will occur.

[0222] For example, if 4 ports of SRS resources are used, assuming rule 2 above, the SRS transmission power of each port becomes 1 / 4 of the total transmission power. However, in 3TX UL transmission, one port portion of the 4 ports is technically unnecessary. In this case, it is also conceivable that the unused port portion will not be transmitted.

[0223] Furthermore, when the SRS resources of ports {1, 2} of the TDM are used,

[0224] • If rule 1 is followed, the SRS transmit power for each port will vary per resource;

[0225] • If rule 2 is followed, the SRS transmit power is the same for each port, but the transmit power used for the SRS resources of port 1 can be assumed to have more transmit power margin (power budget).

[0226] Furthermore, when the SRS resources of ports {1, 1, 1} under TDM are used, in either rule 1 / 2, the transmit power of each port can achieve / reach 1 / 3 of the total transmit power (each is allocated 1 / 3).

[0227] In this case, when the SRS resources of ports {1,2} / {1,1,1} of TDM are used, it can be interpreted that, as long as the rules based on the existing specifications are followed, the total SRS transmission power within a certain OFDM symbol will actually exceed (be greater than) the available transmission power.

[0228] In other words, if existing rules are applied directly to 3TX UEs, the transmit power of each port will be wasted or set to an unattainable power (exceeding the actual usable transmit power), raising concerns about the inability to properly control transmit power.

[0229] This problem is not limited to codebook-based SRS transmission, but is also envisioned for non-codebook-based SRS transmission.

[0230] <Topic 5>

[0231] Furthermore, regarding the SRS discarding rules, existing specifications stipulate that they are implemented on a symbolic unit basis. However, in the aforementioned 3Tx UL transmission, it is not explicitly stated how the SRS discarding rules should be applied.

[0232] For example, if the SRS resources of ports {1,2} under TDM or ports {1,1,1} under TDM are used, the existing specifications need to be extended.

[0233] <Topic 6>

[0234] Furthermore, regarding the configuration of SRS resources, further expansion is under investigation. For example, when the SRS resources of ports {1, 2} are used (regardless of FDM (Frequency Division Multiplexing) / TDM (Time Division Multiplexing), a minimum number of SRS resources needs to be expanded.

[0235] In this case, if the various regulations related to 3Tx UL (e.g., PUSCH) transmission are unclear, there is a concern that the UE may not be able to control proper UL transmission.

[0236] Therefore, the inventors of this invention conceived of the wireless communication method involved in this disclosure.

[0237] The embodiments disclosed herein will now be described in detail with reference to the accompanying drawings. The wireless communication methods described in each embodiment can be applied individually or in combination.

[0238] (Various replacements, etc.)

[0239] In this disclosure, "A / B" and "at least one of A and B" may be used interchangeably. Furthermore, in this disclosure, "A / B / C" may also mean "at least one of A, B, and C".

[0240] In this disclosure, the terms notification, activation, deactivation, indication (or indication), selection, configuration, update, and determination can be used interchangeably. Similarly, the terms support, control, ability to control, operation, and ability to operate can also be used interchangeably.

[0241] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-level parameters, fields, Information Elements (IE), settings, etc., can be interchanged. Similarly, Medium Access Control (MAC Control Element (CE), update commands, activation / deactivation commands, etc., can also be interchanged.

[0242] In this disclosure, higher-layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.

[0243] In this disclosure, MAC signaling may also use, for example, a MAC Control Element (MACCE) or a MAC Protocol Data Unit (PDU). Broadcast information may also be, for example, a Master Information Block (MIB), a System Information Block (SIB), Minimum System Information (Remaining Minimum System Information (RMSI)), or Other System Information (OSI).

[0244] In this disclosure, physical layer signaling may also be, for example, downlink control information (DCI), uplink control information (UCI), etc.

[0245] In this disclosure, indexes, identifiers (IDs), indicators, resource IDs, etc., can be used interchangeably. Sequences, lists, sets, groups, clusters, subsets, etc., can also be used interchangeably.

[0246] In this disclosure, the following terms are used: 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). Channel (PUCCH) groups, PUCCH resource groups, resources (e.g., reference signal resources, SRS resources), resource sets (e.g., reference signal resource sets), CORESET pools, downlink transmission configuration indication states (TCI states) (DL TCI states), uplink TCI states (UL TCI states), unified TCI states, common TCI states, quasi-co-location (QCL) and QCL concepts can also be interchanged.

[0247] In this disclosure, TPMI and TPMI index can be used interchangeably. Port and antenna port can also be used interchangeably. 8TX (8 transmit) can also refer to 8 ports or 8 antenna ports. Port / antenna port can also refer to the port / antenna port used for UL (e.g., SRS / PUSCH) transmission. In this disclosure, SRS resource set and resource set can also be used interchangeably. Coherence group and SRS resource set can also be used interchangeably.

[0248] This disclosure primarily describes 8TX, but the same principle applies to 5TX, 6TX, 7TX, TX of 8 or more, and TX of 4 or less. In the following embodiments, "8" can also be replaced with "n" (where n is any integer). In this case, those skilled in the art can conceive of a maximum value of "n" for the number of layers / ports, etc., which has been described with an assumed maximum value of "8" and can appropriately replace it.

[0249] In addition, in this disclosure, "having the ability to..." and "the ability to support / report..." can be used interchangeably.

[0250] In this disclosure, rank, transmission rank, number of layers, and number of antenna ports can be interchanged. Furthermore, the application of one codeword and a layer count of four or less can also be interchanged. The application of two codewords and a layer count greater than four can also be interchanged.

[0251] In this disclosure, tables may also be interchanged with one or more tables.

[0252] In this disclosure, the operations of allocation, partitioning, and division can be substituted for each other.

[0253] In this disclosure, the terms drop, cancel, puncture, rate match, postpone, and do not send can also be rewritten interchangeably.

[0254] Furthermore, in the following embodiments, DCI may also refer to the DCI of at least one of the scheduling PUSCH and PDSCH (e.g., DCI format 0_x, 1_x (where x is an integer)). Furthermore, the following embodiments are based on codebook-based transmission (PUSCH), but are not limited thereto.

[0255] (Wireless communication method)

[0256] The embodiments of this disclosure can be broadly categorized into the following situations.

[0257] • First implementation method: Temporal domain limitations for codebooks for 3TX UEs.

[0258] • Second implementation method: Size of the SRI field in 3TX PUSCH transmission.

[0259] • Third implementation method: The correspondence between 3TX PUSCH transmission and MTRP PUSCH transmission.

[0260] Fourth implementation method: Association between PTRS port and DMRS port in 3TX PUSCH transmission.

[0261] Fifth implementation method: Allocation (segmentation) of SRS transmission power in 3TX PUSCH transmission.

[0262] • Sixth implementation method: Discarding rules for 3TX PUSCH transmissions.

[0263] • Seventh implementation: Further extension of the SRS settings sent by 3TX PUSCH.

[0264] Based on these, the various implementation methods will be described below.

[0265] In this disclosure, each implementation method / option can be applied individually or in combination.

[0266] The association between the precoding matrix W and the TPMI index in this disclosure can also be defined in Specification 1 (Physical channels and modulation / Uplink / Physical channels / Physical uplink shared channel / Precoding) for physical channels and modulation. In this disclosure, this association, table Px, TPMI table, precoding matrix table, and precoder table can also be interchanged.

[0267] The association between the precoding information (TPMI) and layer number (TRI) in this disclosure, and the index (precoding information field value), can also be defined in Specification 2 (Multiplexing and Channel Coding / Downlink Transport Channels and Control Information / Downlink Control Information / DCI Formats / DCI Format 0_1) used for multiplexing and channel coding. In this disclosure, the association, table Dx, TRI / TPMI indication table, DCI indication table, and precoding information table can also be interchanged.

[0268] In this disclosure, the precoding matrix and the precoder can be interchanged.

[0269] In the following embodiments, the precoding matrix / precoder may also refer to a non-interventional encoder.

[0270] In this disclosure, the 3 ports, 3 Tx, and 3 antenna ports are interchangeable. That is, in this disclosure, the ports, Tx, and antenna ports can be used interchangeably.

[0271] In this disclosure, 3-port PUSCH transmission, 3Tx PUSCH transmission, and PUSCH transmission using 3 antenna ports can be interchanged.

[0272] In this disclosure, the size relationship of resources / resource sets / resource groups associated with SRS is represented by resource < resource group < resource set, but is not limited thereto.

[0273] In the following embodiments, the quantity (e.g., 0, 1, 2, etc.) corresponding to a certain index (e.g., TPMI index, antenna port index, etc.) can be replaced with a quantity with # (e.g., #0, #1, #2, etc.).

[0274] In this disclosure, the UE can be configured / indicated to a codebook (a subset of the codebook) for the 3TX UE.

[0275] For example, for an SRS resource set whose purpose is set as a codebook, the possible settings of the SRS resources (the correspondence between resource sets / resources) can be at least one of the following modes (also known as setting modes). That is, the UE can control UL transmission (transmission of PUSCH / SRS) based on the following modes.

[0276] Figures 11A to 11D This is a conceptual diagram representing the resource set / resource correspondence (modes 1-4) in the codebook for 3TX UE. Figure 11A Corresponding to mode 1, Figure 11B Corresponding to mode 2, Figure 11C Corresponding to mode 3, Figure 11D This corresponds to mode 4.

[0277] <Mode 1>

[0278] • Associate one SRS resource set with one 1-port SRS resource and one 2-port SRS resource. That is, one SRS resource set contains one 1-port SRS resource and one 2-port SRS resource (see [link to documentation]). Figure 11A ).

[0279] <Mode 2>

[0280] • Associate one SRS resource set with three one-port SRS resources. That is, one SRS resource set contains three one-port SRS resources #1 to #3 (see...) Figure 11B ).

[0281] <Mode 3>

[0282] • Associate one SRS resource set with two 1-port SRS resources and two 2-port SRS resources. That is, one SRS resource set contains two 1-port SRS resources and two 2-port SRS resources.

[0283] Additionally, in Mode 3, multiple (4) SRS resources are divided (subset) into multiple (2) groups. These multiple groups can also be referred to as SRS resource groups.

[0284] Each group (SRS resource group) contains two SRS resources (one 1-port SRS resource and one 2-port SRS resource). For example, one group (also referred to as SRS resource group #1, or group one) may have a first 1-port SRS resource (1-port SRS resource #1) and a first 2-port SRS resource (2-port SRS resource #1), while another group (also referred to as SRS resource group #2, or group two) may have a second 1-port SRS resource (1-port SRS resource #2) and a second 2-port SRS resource (2-port SRS resource #2) (see [link]). Figure 11C ).

[0285] <Mode 4>

[0286] • Associate one SRS resource set with six one-port SRS resources. That is, one SRS resource set contains six one-port SRS resources #1 to #6.

[0287] Additionally, in Mode 4, multiple (6, or a multiple of 3 (3N)) SRS resources are divided (subset) into multiple (2, or N) groups. These multiple groups can also be referred to as SRS resource groups.

[0288] Each group (SRS resource group) contains 3 SRS resources (3 one-port SRS resources). For example, one group (also known as SRS resource group #1, or group one) may have the first to third one-port SRS resources (one-port SRS resources #1 to #3), and another group (also known as SRS resource group #2, or group two) may have the fourth to sixth one-port SRS resources (one-port SRS resources #4 to #6) (see...). Figure 11D ).

[0289] As shown in patterns 1 to 4 above, one SRS resource set can be associated with multiple (more than 2) SRS resources. That is, one SRS resource set can contain multiple (more than 2) SRS resources (e.g., 2 to 6).

[0290] In particular, in modes 3 and 4, multiple SRS resources within a single SRS resource set can also constitute / form multiple groups (the SRS resource groups mentioned above). In this case, each group can contain at least two (or more) SRS resources.

[0291] The following implementation methods can also be applied to UL transmission control based on the above-described modes 1 to 4.

[0292] <First Implementation Method>

[0293] The first implementation corresponds to the aforementioned issue 1 and relates to time-domain limitations of the codebook for 3TX UEs.

[0294] In the following modes 1 to 4, for one SRS resource set whose purpose is set as a codebook, the limitations / constraints / conditions regarding the application of any of the modes 1 to 4 are explained. That is, the UE can control UL transmission (PUSCH / SRS transmission) based on the following limitations / constraints / conditions. In addition, the limitations / constraints / conditions shown below can also be referred to as time-domain limitations / constraints / conditions.

[0295] [Method 1]

[0296] For an SRS resource set whose purpose is set as a codebook, the following Alt1~Alt3 restrictions can be applied when Mode 1 above is applied (associating an SRS resource set with a 1-port SRS resource and a 2-port SRS resource).

[0297] Figures 12A to 12C This is a conceptual diagram illustrating an example of a time-domain SRS mapping according to Embodiment 1 of the first implementation. Figure 12A Corresponding to Alt1, Figure 12B Corresponding to Alt2 (Alt2A). Figure 12C This corresponds to Alt3 (Alt3A). Additionally, Figures 12A to 12C This is for the convenience of focusing only on examples in the time domain, without considering the frequency domain.

[0298] (Alt1)

[0299] Two SRS resources are transmitted in the same OFDM symbol within the same time slot (see...). Figure 12A ).

[0300] (Alt2)

[0301] Two SRS resources can be transmitted in different OFDM symbols within the same time slot (see...). Figure 12B ).

[0302] (Alt2A)

[0303] For example, two SRS resources can be transmitted in consecutive OFDM symbols within the same time slot (see...). Figure 12B ).

[0304] (Alt3)

[0305] Two SRS resources can be transmitted in different OFDM symbols within the same / different time slots (see...) Figure 12C ).

[0306] (Alt3A)

[0307] For example, two SRS resources can be transmitted in consecutive OFDM symbols within the same / different time slots (see...). Figure 12C ).

[0308] <Note>

[0309] Furthermore, considering the frequency domain (with the constraints of the applied frequency domain), the same comb value can be applied in a combination of {1, 2} port SRS resources within a single SRS resource set. This is because, in this combination, the RS density of each symbol at each port is equal.

[0310] For example, the comb setting for a 1-port SRS resource can be half that of a 2-port SRS resource. Specifically, it could be that Comb2 is applied to the 1-port SRS resource and Comb4 is applied to the 2-port SRS resource. This is because, in Alt2 / 3, it is assumed that the total transmission power between symbols is the same, and the transmission power of each symbol on each port is equal.

[0311] Regardless of the port (SRS resource), the same resource element (subcarrier) may not be shared. Alternatively, for at least one of the 1-port / 2-port SRS resources, the same resource element (subcarrier) may be shared.

[0312] [Method 2]

[0313] For an SRS resource set whose purpose is set as a codebook, when Mode 2 above is applied (associating 1 SRS resource with 3 1-port SRS resources), the following Alt1~Alt3 restrictions can be applied.

[0314] (Alt1)

[0315] The three SRS resources were transmitted in the same OFDM symbol within the same time slot.

[0316] (Alt2)

[0317] Three SRS resources can be transmitted in different OFDM symbols within the same time slot.

[0318] (Alt2A)

[0319] For example, three SRS resources can be transmitted in consecutive OFDM symbols within the same time slot.

[0320] (Alt3)

[0321] Three SRS resources can be transmitted in different OFDM symbols within the same / different time slots.

[0322] (Alt3A)

[0323] For example, three SRS resources can be transmitted in consecutive OFDM symbols within the same / different time slots.

[0324] <Note>

[0325] Furthermore, considering the frequency domain (with the constraints of the applied frequency domain), the same comb value can be applied in a combination of {1,1,1} port SRS resources within a single SRS resource set. This is because, in this combination, the RS density of each symbol at each port is equal.

[0326] For example, the comb setting for a 1-port SRS resource can be half that of a 2-port SRS resource. Specifically, it could be that Comb2 is applied to the 1-port SRS resource and Comb4 is applied to the 2-port SRS resource. This is because, in Alt2 / 3, it is assumed that the total transmission power between symbols is the same, and the transmission power of each symbol on each port is equal.

[0327] Regardless of the port (SRS resource), the same resource element (subcarrier) may not be shared (e.g., Alt1). Alternatively, the same resource element (subcarrier) may be shared for all SRS resources (e.g., except Alt1). Furthermore, within Alt1, the same resource element (subcarrier) may be shared for all SRS resources. In this case, the sequences set in each SRS resource can also be assigned different coefficients (e.g., cyclic shift values).

[0328] [Method 3]

[0329] For an SRS resource set whose purpose is set as a codebook, the following Alt1~Alt3 restrictions can be applied when Mode 3 above is applied (associating one SRS resource with one 1-port SRS resource and one 2-port SRS resource).

[0330] (Alt1)

[0331] Two SRS resources within a group are transmitted in the same OFDM symbol within the same time slot.

[0332] (Alt2)

[0333] Two SRS resources within a group can be transmitted in different OFDM symbols within the same time slot.

[0334] (Alt2A)

[0335] For example, two SRS resources within a group can be transmitted in consecutive OFDM symbols within the same time slot.

[0336] (Alt3)

[0337] Two SRS resources within a group can be transmitted in different OFDM symbols in the same / different time slots.

[0338] (Alt3A)

[0339] For example, two SRS resources within a group can be transmitted in consecutive OFDM symbols in the same / different time slots.

[0340] <Note>

[0341] Furthermore, considering the frequency domain (with the constraints of the applied frequency domain), the same comb value can be applied in the combination of {1, 2} port SRS resources within a single SRS resource group. This is because, in this combination, the RS density of each symbol at each port is equal.

[0342] For example, the comb setting for a 1-port SRS resource can be half that of a 2-port SRS resource. Specifically, it could be that Comb2 is applied to the 1-port SRS resource and Comb4 is applied to the 2-port SRS resource. This is because, in Alt2 / 3, it is assumed that the total transmission power between symbols is the same, and the transmission power of each symbol on each port is equal.

[0343] Regardless of the port (SRS resource), the same resource element (subcarrier) may not be shared. Alternatively, for at least one of the 1-port / 2-port SRS resources, the same resource element (subcarrier) may be shared.

[0344] [Method 4]

[0345] For an SRS resource set whose purpose is set as a codebook, when Mode 4 above is applied (associating 6 1-port SRS resources with 1 SRS resource set), the following Alt1~Alt3 restrictions can be applied.

[0346] (Alt1)

[0347] Three SRS resources within a group are transmitted in the same OFDM symbol within the same time slot.

[0348] (Alt2)

[0349] Three SRS resources within a group can be transmitted in different OFDM symbols within the same time slot.

[0350] (Alt2A)

[0351] For example, three SRS resources within a group can be transmitted in consecutive OFDM symbols within the same time slot.

[0352] (Alt3)

[0353] Three SRS resources within a group can be transmitted in different OFDM symbols in the same or different time slots.

[0354] (Alt3A)

[0355] For example, three SRS resources within a group can be transmitted in consecutive OFDM symbols in the same / different time slots.

[0356] <Note>

[0357] Furthermore, considering the frequency domain (with the constraints of the applied frequency domain), the same comb value can be applied in a combination of {1,1,1} port SRS resources within a single SRS resource group. This is because, in this combination, the RS density of each symbol at each port is equal.

[0358] For example, the comb setting for a 1-port SRS resource can be half that of a 2-port SRS resource. Specifically, it could be that Comb2 is applied to the 1-port SRS resource and Comb4 is applied to the 2-port SRS resource. This is because, in Alt2 / 3, it is assumed that the total transmission power between symbols is the same, and the transmission power of each symbol on each port is equal.

[0359] Regardless of the port (SRS resource), the same resource element (subcarrier) may not be shared (e.g., Alt1). Alternatively, the same resource element (subcarrier) may be shared for all SRS resources (e.g., except Alt1). Furthermore, within Alt1, the same resource element (subcarrier) may be shared for all SRS resources. In this case, the sequences set in each SRS resource can also be assigned different coefficients (e.g., cyclic shift values).

[0360] According to this implementation, the UE can appropriately control the PUSCH transmission using the 3-antenna port based on specific conditions (time-domain constraints).

[0361] <Second Implementation Method>

[0362] The second implementation corresponds to Problem 2 above and is related to the size of the SRI field. Figure 13A and Figure 13B This is a diagram illustrating an example of the SRI field involved in the second embodiment.

[0363] The UE can envision the following modes 1 to 4 in PUSCH transmission using 3 antenna ports. Modes 1 to 4 correspond to modes 1 to 4 mentioned above.

[0364] [Method 1]

[0365] For an SRS resource set whose purpose is set as a codebook, when Mode 1 above is applied (associating one SRS resource set with one 1-port SRS resource and one 2-port SRS resource), the PUSCH transmission uses a precoder to correspond to the two SRS resources within the one SRS resource set (Case 1 above).

[0366] In this case, the SRI indication in the DCI is not required. For example, the SRI field can be 0 bits.

[0367] [Method 2]

[0368] For a set of SRS resources whose purpose is set as a codebook, when mode 2 above is applied (associating 3 port 1 SRS resources with 1 SRS resource), the PUSCH transmission uses a precoder to correspond to the 3 SRS resources within the set of 1 SRS resources (case 2 above).

[0369] In this case, the SRI indication in the DCI is not required. For example, the SRI field can be 0 bits.

[0370] [Method 3]

[0371] For a set of SRS resources whose purpose is set as a codebook, when Mode 3 above is applied (associating one SRS resource with one 1-port SRS resource and one 2-port SRS resource), as described above, multiple (4) SRS resources are divided (subset) into multiple (2) groups. Each group (SRS resource group) contains 2 SRS resources (one 1-port SRS resource and one 2-port SRS resource).

[0372] In this case, the PUSCH transmission precoder corresponds to one SRS resource group (containing two SRS resources) indicated by the SRI field within DCI format 0_1 / 0_2. This SRS resource group can be equivalent to scenario 1 described above.

[0373] In this case, the number of bits in the SRI field included in the DCI is determined by ceil(log2(N)). SRS，group)) represents. Here, N SRS，group This is the number of SRS resource groups.

[0374] Furthermore, as a variation, this number of bits can also be calculated using ceil(log2(N)). SRS / 2)) represents. Here, N is... SRS It can be the number of SRS resources within the SRS resource set (including both 1-port SRS resources and 2-port SRS resources).

[0375] Furthermore, as another variation, this number of bits can also be calculated using ceil(log2(N)). SRS，1-port ), or ceil(log2(N) SRS，2-port )) represents. Here, N SRS，1-port N can be the number of 1-port SRS resources within (and contained in) the SRS resource set. SRS，2-port It can be the number of 2-port SRS resources within (included in) the SRS resource set.

[0376] <Specific example>

[0377] like Figure 13A As shown, the bit field mapped to index 0 (SRI field #0) indicates the first SRS group (SRS resource group #1). This group contains one 1-port SRS resource (first 1-port SRS resource) and one 2-port SRS resource (first 2-port SRS resource).

[0378] Similarly, the bit field mapped to index 1 (SRI field #1) indicates the second SRS group (SRS resource group #2). This group contains one 1-port SRS resource (second 1-port SRS resource) and one 2-port SRS resource (second 2-port SRS resource).

[0379] [Method 4]

[0380] For one SRS resource set whose purpose is set as a codebook, when the above-mentioned Mode 4 is applied (one SRS resource set is associated with six 1-port SRS resources), the multiple (six) SRS resources are divided (subset) into multiple (two) groups. Each group (SRS resource group) contains three SRS resources (three 1-port SRS resources).

[0381] In this case, the PUSCH transmission precoder corresponds to one SRS resource group (containing 3 SRS resources) indicated by the SRI field within DCI format 0_1 / 0_2. This SRS resource group can be equivalent to scenario 2 described above.

[0382] In this case, the number of bits in the SRI field included in the DCI is determined by ceil(log2(N)).SRS，group )) represents. Here, N SRS，group This is the number of SRS resource groups.

[0383] Furthermore, as a variation, this number of bits can also be calculated using ceil(log2(N)). SRS / 3)) represents. Here, N is... SRS It can be the number of SRS resources (1 port SRS resource) contained within the SRS resource set.

[0384] <Specific example>

[0385] like Figure 13B As shown, the bit field mapped to index 0 (SRI field #0) indicates the first SRS group (SRS resource group #1). This group contains three 1-port SRS resources (first 1-port SRS resources).

[0386] Similarly, the bit field mapped to index 1 (SRI field #1) indicates the second SRS group (SRS resource group #2). This group contains three 1-port SRS resources (second 1-port SRS resources).

[0387] [other]

[0388] SRS resources for DCI format 0_2 are provided via the high-level parameter srs-ResourceSetToAddModListDCI-0-2, which is associated with a list of SRS resource sets. Similarly, SRS resources for DCI format 0_1 ​​are provided via the high-level parameter srs-ResourceSetToAddModListDCI-0-1, which is associated with a list of SRS resource sets.

[0389] For example, if the UE is configured to monitor DCI format 0_2, the UE can envision the following scenario.

[0390] In the case where the SRS resource set provided for DCI format 0_1 / 0_2 includes 1-port SRS resources and 2-port SRS resources.

[0391] • The UE is designed to be configured with N in the SRS resource set used in DCI format 0_2. SRS，0_2，1-port One 1-port SRS resource. In this case, the SRS resource set consists of the initial 1-port SRS resource within the SRS resource set configured for DCI format 0_1.

[0392] • The UE is designed to be configured with N in the SRS resource set used in DCI format 0_2. SRS，0_2，2-portA 2-port SRS resource. In this case, the SRS resource set is composed of the initial 2-port SRS resources within the SRS resource set configured for DCI format 0_1.

[0393] [Variation Example 1]

[0394] When the UE is configured to transmit 3-port PUSCH (3Tx / 3-layer PUSCH), it is not expected (not expected to be configured) that the UE be configured with more than the number of SRS resources shown in any of the following options in the corresponding SRS resource set.

[0395] Option 1: 2 SRS resources;

[0396] Option 2: 3 SRS resources.

[0397] Option 1 above corresponds to the case where one 1-port SRS resource and one 2-port SRS resource are configured (Case 1 above), i.e., a combination of antenna ports {1, 2}. Option 2 corresponds to the case where three 1-port SRS resources are configured (Case 1 above), i.e., a combination of antenna ports {1, 1, 1}.

[0398] According to Variation 1, since the SRI indication is not included (and is not required) in the scheduling DCI, there is no need for an extended / UE implementation for 3-port PUSCH transmission.

[0399] [Variation Example 2]

[0400] When the UE is configured for 3-port PUSCH transmission (3Tx / 3-layer PUSCH transmission), the number of bits (bit width) of the SRI field can be replaced by the sum of the SRS resource counts, as described above: ceil(log2(N)). SRS ), or ceil(log2(N) SRS，group (), for example, can be represented by the following formula.

[0401]

[0402] According to Variation 2, existing SRI instructions (for non-codebook-based PUSCH transmissions) can be reused / carried forward. Furthermore, there is no need to consider (dedicated) TPMI for 3-port PUSCH transmissions.

[0403] According to this implementation, the UE can appropriately control the PUSCH transmission using the 3-antenna port based on the presence or absence of the SRI indication (SRI field).

[0404] <Third Implementation Method>

[0405] The third embodiment corresponds to Problem 2 above and relates to the correspondence with MTRP PUSCH.

[0406] The UE can envision the correspondence between the first / second implementation described above and the MTRP PUSCH based on the following options 1-2 (whether the application of both is possible). In addition, the MTRP PUSCH shown below can refer to the transmission of MTPPPUSCH for Rel.17, the transmission of a single DCI STxMP SDM / SFN PUSCH for Rel.18, or the transmission of multiple DCI STxMP PUSCH for Rel.18 (all of which are existing multi-TRP PUSCH transmissions).

[0407] [Option 1]

[0408] The UE does not assume that the 3-port PUSCH transmission of this disclosure or the existing multi-TRP PUSCH transmission will be activated. Each PUSCH transmission mode can be activated by following at least one of the following.

[0409] • Port 3 PUSCH transmission can be activated by new higher-layer parameters, or by setting port 3 SRS resources, or as described in the first embodiment above, it can be considered to be activated by setting SRS resources / SRS resource sets.

[0410] • MTRP PUSCH transmission for Rel.17 can be considered as being activated when two codebook / non-codebook SRS resource sets are set.

[0411] • Single DCI STxMP SDM PUSCH transmission for Rel.18 can be considered as being activated when two codebook / non-codebook SRS resource sets are set, or when the multipanel scheme is set to SDM (multipanelScheme='SDMScheme').

[0412] • Single DCI STxMP SFM PUSCH transmission for Rel.18 can be considered as being activated when two codebook / non-codebook SRS resource sets are set, or when the multipanel scheme is set to SFM (multipanelScheme='SFMScheme').

[0413] • Multi-DCI STxMP PUSCH transmission for Rel.18 can be considered as being activated when two codebook / non-codebook SRS resource sets are set, and when two CORESET pool indices are set, or when specific parameters (e.g., enableSTx2PofmDCI) are provided.

[0414] [Option 2]

[0415] Both the 3-port PUSCH transmission of this disclosure and the existing multi-TRP PUSCH transmission can be activated. That is, the UE can envision that both the 3-port PUSCH transmission of this disclosure and the existing multi-TRP PUSCH transmission are activated.

[0416] The first embodiment described above can also be used for existing multi-TRP PUSCH transmission. For example, when two SRS resource sets are configured, each SRS resource set can be configured as the SRS resource set of the first embodiment (for 3-port PUSCH transmission).

[0417] The second embodiment described above can also be used for existing multi-TRP PUSCH transmission. For example, when two SRS resource sets are set and two SRI fields are indicated in the DCI, each SRI field can be the SRI field of the second embodiment.

[0418] According to this implementation, it is possible to appropriately determine whether the application of both 3-port PUSCH transmission and existing multi-TRP PUSCH transmission is feasible.

[0419] <Fourth Implementation Method>

[0420] The fourth embodiment corresponds to Problem 3 above and relates to the association between the PTRS port and the DMRS port in 3TX PUSCH transmission. Figure 14A and Figure 14B This is a diagram illustrating an example of the PTRS-DMRS association field involved in the fourth embodiment. Figure 15 This is a diagram illustrating a variation of the PTRS-DMRS association field according to the fourth embodiment.

[0421] The UE can control the transmission of PTRS by applying the association shown below in the 3-port PUSCH transmission.

[0422] With two PTRS ports configured, the UE can be instructed on the association between the PTRS ports and the DMRS ports via the DCI. In other words, the association between the PTRS ports and the DMRS ports can be included within the DCI.

[0423] The code point values ​​in the table shown in Figure 14 select two DMRS ports from the scheduled DMRS ports. Two PTRS ports, #0 and #1, are associated with the two selected DMRS ports respectively. PTRS port #0 is associated with the initially (first) selected DMRS port, and PTRS port #1 is associated with the next (second) selected DMRS port.

[0424] As an example, such as Figure 14A As shown, the code point values ​​(value=0, 1, 2, 3) in the table jointly indicate the DMRS ports for PTRS ports #0 and #1.

[0425] Specifically, code point value 0 indicates the first and second scheduled DMRS ports. Code point value 1 indicates the first and third scheduled DMRS ports. Code point value 2 indicates the second and third scheduled DMRS ports. Code point value 3 is reserved.

[0426] As another example, such as Figure 14B As shown, the code point values ​​(value=0, 1, 2, 3) in the table specifically (separately) indicate the DMRS port for PTRS port #0 and the DMRS port for PTRS port #1.

[0427] Specifically, code point value 0 (value=0) indicates the first scheduled DMRS port. This first scheduled DMRS port is associated with PTRS port #0. Furthermore, code point value 0 (value=0) indicates the second scheduled DMRS port. This second scheduled DMRS port is associated with PTRS port #1.

[0428] The code point value 1 indicates the first scheduled DMRS port. This first scheduled DMRS port is associated with PTRS port #0. Additionally, the code point value 1 indicates the third scheduled DMRS port. This third scheduled DMRS port is associated with PTRS port #1.

[0429] Code point value 2 indicates the second scheduled DMRS port. This second scheduled DMRS port is associated with PTRS port #0. Additionally, code point value 2 indicates the third scheduled DMRS port. This third scheduled DMRS port is associated with PTRS port #1.

[0430] The code point value 3 (value=3) is reserved.

[0431] According to the table in Figure 14, the association between the PTRS port and the DMRS port can be indicated without increasing the number of bits (maintaining 2 bits).

[0432] As a variation, such as Figure 15 As shown, a 1-bit table can also be specified. In Figure 15 In this context, association is only performed for the DMRS port of PTRS port #0; association for PTRS port #1 is not required.

[0433] Specifically, code point value 0 indicates the first scheduled DMRS port. This first scheduled DMRS port shares PTRS port #0. That is, this first scheduled DMRS port is the DMRS port mapped to PUSCH antenna ports 1000 and 1002.

[0434] The code point value 1 indicates the second scheduled DMRS port. This second scheduled DMRS port shares PTRS port #0. That is, this second scheduled DMRS port is the DMRS port mapped to PUSCH antenna ports 1000 and 1002.

[0435] The code point value 3 (value=3) is reserved.

[0436] As mentioned above, in Figure 15 In this example, no indication is specified for PTRS port #1. It is assumed that PTRS port #1 is associated with the DMRS port mapped to PUSCH antenna port 1001.

[0437] As another variation, PUSCH antenna ports 1000 and 1001 can also share PTRS port #0. In this case, PUSCH antenna port 1002 can also share / use PTRS port #1.

[0438] As another variation, when only one PTRS port is configured, the existing association between the PTRS port and the DMRS port can also be applied. In this case, the code point value 3 (value=3) can be reserved.

[0439] According to this implementation, the UE takes into account the association between the PTRS port and the DMRS port, and can properly control the transmission of port 3 PUSCH without increasing overhead.

[0440] <Fifth Implementation Method>

[0441] The fifth embodiment corresponds to the above-mentioned problem 4 and relates to the splitting of SRS transmission power in 3TX PUSCH transmission.

[0442] The fifth implementation can be classified into implementations 5-1 to 5-3 based on the type (number of ports) of the SRS resources set. The UE can control the allocation (segmentation) of SRS transmission power according to (following) the rules specified in each implementation.

[0443] [Implementation Method 5-1]

[0444] When the UE is configured to transmit via 3TX PUSCH and 4-port SRS resources are allocated for UL channel probing, the UE can divide the transmit power among the 3 ports. In this case, no transmit power needs to be allocated to the remaining 1 port. That is, the UE divides the total transmit power used for the 4 ports among the 3 ports.

[0445] By equally distributing 1 / 3 of the transmit power intended for port 4 to each of the three ports, the SRS transmit power of each port can be maximized. In other words, by allocating the power originally intended for port 4 to the three ports, no portion of the power intended for port 4 is wasted, and power can be allocated efficiently.

[0446] [Implementation Method 5-2]

[0447] When the UE is configured to transmit 3TX PUSCH and is configured / transmitted with {1, 2} port SRS resources in TDM mode (manner / scheme) for UL channel probing, the UE can divide the transmission power among (multiple) ports that are transmitted in one OFDM symbol.

[0448] In this case, applying existing rules (such as rule 1 above) can maximize the SRS transmission power of each port (making the most efficient and flexible use of it).

[0449] [Implementation Method 5-2']

[0450] When the UE is configured to transmit 3TX PUSCH and is configured / transmitted with {1, 2} port SRS resources in TDM mode (manner / scheme) for UL channel probing, the UE can divide the transmission power among the (multiple) ports transmitted in one OFDM symbol. In this case, the UE can consider the minimum transmission power of each SRS port among all SRS ports.

[0451] According to this rule, the transmit power for a 1-port SRS resource can be approximately half the combined transmit power for a 2-port SRS resource. In this case, the UE / gNB can assume the same (or equivalent) transmit power for all ports. In particular, the gNB can easily perform UL CSI calculations.

[0452] [Implementation Method 5-3]

[0453] When the UE is configured to transmit 3TX PUSCH and is configured / transmitted with {1,1,1} port SRS resources in TDM mode (manner / scheme) for UL channel probing, the UE can divide the transmission power among (multiple) ports that are transmitted in one OFDM symbol.

[0454] In this case, applying existing rules (such as rule 1 above) can maximize the SRS transmission power of each port (making the most efficient and flexible use of it).

[0455] [Implementation Method 5-3']

[0456] When the UE is configured to transmit 3TX PUSCH and multiple SRS resources are configured / transmitted in FDM mode (i.e., within 1 OFDM symbol) for UL channel probing, the UE can divide the transmission power based on at least one of the following options.

[0457] (Option 1)

[0458] In this option, the UE can follow the steps below to perform transmit power splitting.

[0459] Step 0: The UE determines the transmit power P of each SRS resource according to existing specifications. SRS .

[0460] Step 1: The UE divides each SRS resource into P segments based on each port within the SRS resource (between ports). SRS .

[0461] Step 2: The UE checks whether the total transmit power exceeds the maximum transmit power limit (e.g., P) through (multiple) SRS resources. CMAX ).

[0462] In step 2,

[0463] • When the total transmission power exceeds the maximum transmission power limit,

[0464] Option 1-1: The UE equally reduces the transmit power for all SRS resources.

[0465] Option 1-1': The UE equally reduces the transmit power for all ports.

[0466] Option 1-2: The UE reduces the transmit power only for specific SRS resources.

[0467] Otherwise (provided the total transmit power does not exceed the maximum transmit power limit), the UE utilizes the transmit power of each port determined in the previous steps (step 0 and step 1).

[0468] (Option 2)

[0469] In this option, the UE can follow the steps below to perform transmit power splitting.

[0470] Step 0: The UE segments P based on the number of SRS resources transmitted within one OFDM symbol (the set number of SRS resources). CMAX For example, when two SRS resources are sent (set), the UE considers P in the power control of each SRS resource. CMAX / 2(P) CMAX Half of it.

[0471] Step 1: The UE considers the segmented P CMAX This is used to calculate the transmission power of each SRS resource.

[0472] Step 2: The UE calculates the transmission power of each port by dividing the transmission power among the set ports (a specific number of ports) for each SRS resource.

[0473] (Option 2)

[0474] In this option, the UE can follow the steps below to perform transmit power splitting.

[0475] Step 0: The UE segments P based on the total number of ports transmitted within one OFDM symbol (the total number of ports as expressed by the following equation (4)). CMAX For example, when two SRS resources are sent (set) (one port 1 SRS resource and one port 2 SRS resource), P CMAX It is divided into 1*1 ports + 1*2 ports = 3 ports (the total number of ports). In this case, P CMAX / 3 becomes the maximum transmit power of the SRS for each port.

[0476]

[0477] Step 1: The UE calculates the transmission power of each SRS resource (e.g., using existing P...).CMAX ).

[0478] Step 2: The UE calculates the transmission power of each port by allocating the transmission power among the SRS resources in the set number of ports.

[0479] Step 3: The UE compares the results of Step 0 and Step 2 to obtain the minimum value. In other words, the UE selects the minimum value between the results of Step 0 and Step 2.

[0480] (Option 3)

[0481] In this option, the UE can follow the steps below to perform transmit power splitting.

[0482] Step 0: The UE determines the transmit power P according to existing specifications. SRS This transmit power refers to the total transmit power of all SRS resources transmitted within one OFDM symbol.

[0483] Step 1: The UE segments P based on the number of SRS resources in this single OFDM symbol. SRS .

[0484] (Option 3)

[0485] In this option, the UE can follow the steps below to perform transmit power splitting.

[0486] Step 0: The UE determines the transmit power P according to existing specifications. SRS This transmit power refers to the total transmit power of all SRS resources transmitted within one OFDM symbol.

[0487] Step 1: The UE segments P based on the total number of ports between all SRS resources in this single OFDM symbol (the total number of ports for all SRS resources). SRS .

[0488] (Note)

[0489] In implementation 5-3', the multiple (two or more) SRS resources can be any of the following.

[0490] Opt1: 3 SRS resources with 1 port.

[0491] Opt2: One 1-port SRS resource and one 2-port SRS resource.

[0492] In addition, multiple SRS resources here need to be set in the same SRS resource set (be contained in the same SRS resource set).

[0493] According to this implementation, the UE can appropriately control (split) the transmission power based on specific rules / conditions.

[0494] <Sixth Implementation Method>

[0495] The sixth implementation corresponds to issue 5 above and relates to the discarding rules for 3TX PUSCH transmissions.

[0496] When the UE is configured to transmit 3TX PUSCH and multiple SRS resources are configured / transmitted in TDM mode (manner / scheme) for UL channel probing, the SRI indicated in slot n is associated with the (multiple) SRS resources identified by that SRI. Here, the SRI satisfies the additional conditions shown in options 1 to 2 below. That is, in this case, the UE determines (controls transmission) the transmission opportunity (timing) of the corresponding (multiple) SRS resources based on options 1 to 2 below. The conditions shown in options 1 to 2 below and the discarding rules can be mutually modified.

[0497] (Option 1)

[0498] Option 1 lists the additional conditions that the SRI should meet in order for the UE to identify / determine the SRS resource.

[0499] (Option 1-1)

[0500] The SRI is associated with the latest SRS resource for each configured SRS resource. For example, if three 1-port SRS resources are configured, the SRI is associated with the latest transmission opportunity for each SRS resource.

[0501] (Options 1-2)

[0502] This SRI is associated with the latest X SRS resources. Here, the value of X is an integer from 1 to 3, which can be predefined by the specification or set / indicated by higher-layer signaling / physical layer signaling.

[0503] (Options 1-3)

[0504] The SRI is associated with multiple SRS resources within a specific time span (time interval). This specific time span can be defined in advance by a specification or set / indicated by higher-layer signaling / physical layer signaling.

[0505] (Option 2)

[0506] Option 2 lists UE operations in cases where the SRI does not meet the additional conditions mentioned above.

[0507] (Option 2-1)

[0508] The UE should not be expected to be instructed to transmit ULs that do not meet the additional conditions. In this case, the NW (gNB) must control the scheduling (SRS resources / transmission opportunities) in a manner that always satisfies the additional conditions.

[0509] (Option 2-2)

[0510] If the SRI does not meet the additional conditions, the UE will not perform (not transmit) the indicated UL transmission.

[0511] According to this implementation, the UE can apply drop rules to 3TX PUSCH transmission. That is, the UE can appropriately control the transmission timing in 3TX PUSCH transmission based on specific conditions.

[0512] <Seventh Implementation Method>

[0513] The seventh implementation corresponds to issue 6 above and relates to further extensions of 3TX PUSCH transmission (especially SRS resource settings).

[0514] When the UE is configured to send 3TX PUSCH and is configured to send codebook-based PUSCH, at least X SRS resources can be configured for the corresponding SRS resource set. The value of X can follow the options 1 to 2 below.

[0515] (Option 1)

[0516] Option 1 lists the candidate values ​​for X.

[0517] (Option 1-1)

[0518] X=1 (the same rule as the existing specifications)

[0519] (Options 1-2)

[0520] X=2 (assuming the SRS resource settings for ports {1, 2})

[0521] (Options 1-3)

[0522] X=3 (assuming the SRS resource settings for port {1, 1, 1})

[0523] (Options 1-4)

[0524] X>3 (Consider other settings)

[0525] (Option 2)

[0526] Option 2 lists the methods for determining X.

[0527] (Option 2-1)

[0528] X can be defined in advance through specifications.

[0529] (Option 2-2)

[0530] X can be set via higher-level signaling (RRC).

[0531] (Options 2-3)

[0532] X can also be set / indicated via higher-layer signaling (MAC CE) / physical layer signaling (DCI).

[0533] The above options can be selectively applied depending on whether the repeated transmission of MTRP PUSCH is configured (e.g., supported in Rel.17). That is, the UE can determine the application (number of SRS resources) of any one (one or more) of the options based on whether the repeated transmission of MTRP PUSCH is configured.

[0534] According to this implementation, the UE can appropriately control the transmission of PUSCH using the 3-antenna port based on specific SRS resource settings.

[0535] <Supplement>

[0536] [Information notification to UE]

[0537] The notification of any information from the network (NW) (e.g., the base station (BS)) to the UE in the above-described embodiments (in other words, the reception of any information from the BS in the UE) can also be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signals), or a combination thereof.

[0538] In the case of the aforementioned notification being made via MAC CE, the MAC CE can also be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not specified in the existing standard.

[0539] In the case of notification via DCI, the notification may also be made through specific fields of the DCI, the Radio Network Temporary Identifier (RNTI) used in the scrambling of the Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0540] Furthermore, the notification of any information to the UE in the above embodiments can also be performed periodically, semi-persistently, or non-periodically.

[0541] [Notification from UE]

[0542] The notification of any information from the UE (for the NW) in the above embodiments (in other words, the transmission / reporting of any information from the UE for the BS) can also be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

[0543] In the case of notification via MAC CE, the MAC CE can also be identified by including a new LCID, which is not specified in the existing standard, in the MAC subheader.

[0544] When the above notification is sent via UCI, PUCCH or PUSCH can also be used.

[0545] Furthermore, the notification of any information from the UE in the above embodiments can also be performed periodically, semi-persistently, or non-periodically.

[0546] [Regarding the application of each implementation method]

[0547] At least one of the above-described implementation methods can also be applied under certain conditions. These specific conditions can be specified in the standard or notified to the UE / BS using higher-layer signaling / physical layer signaling.

[0548] At least one of the above-described implementation methods may also be applied only to UEs that have reported a specific UE capability or UEs that support that specific UE capability.

[0549] This specific UE capability can also represent at least one of the following:

[0550] • Supports specific processing / operation / control / information related to at least one of the above embodiments;

[0551] • Supports 3TX UL (PUSCH) transmission;

[0552] • Supports various antenna layouts / number of antenna groups.

[0553] • Supported coherent groups;

[0554] • Supports both 3TX UL transmission and MTRP PUSCH transmission;

[0555] • Supports association between PTRS and DMRS ports;

[0556] • Supports the allocation of SRS transmit power in 3TX PUSCH transmission;

[0557] • Supports discarding rules for 3TX PUSCH transmissions;

[0558] • Further expansion of SRS settings supporting 3TX PUSCH transmission.

[0559] Furthermore, the aforementioned specific UE capabilities can be capabilities that are applied across the entire frequency (commonly regardless of frequency), capabilities that are applied to each frequency (e.g., one or a combination of cells, bands, band combinations, BWPs, component carriers, etc.), capabilities that are applied to each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), capabilities that are applied to each subcarrier spacing (SCS), or capabilities that are applied to each feature set (FS) or feature set per component-carrier (FSPC).

[0560] Furthermore, the aforementioned specific UE capabilities can be either capabilities that are applied across the entire duplex mode (commonly regardless of the duplex mode) or capabilities that are specific to each duplex mode (e.g., Time Division Duplex (TDD) and Frequency Division Duplex (FDD)).

[0561] Furthermore, at least one of the above embodiments can also be applied when the UE is set / activated / triggered by specific information associated with the above embodiments (or performs the operations of the above embodiments) via higher-layer signaling / physical layer signaling. For example, the specific information may be information indicating support for activating 8TX UL transmission, support for various different antenna layouts / antenna group numbers, arbitrary RRC parameters for a specific version (e.g., Rel.18 / 19), etc.

[0562] Even if at least one of the aforementioned specific UE capabilities is not supported, or if the aforementioned specific information is not set, the UE may, for example, apply the operation of Rel.15 / 16.

[0563] (Postscript)

[0564] Regarding one embodiment of this disclosure (the fifth embodiment), the invention is described below.

[0565] [Postscript 1]

[0566] A terminal having:

[0567] The receiving unit receives a codebook transmitted via the uplink (UL) using three antenna ports (3TX); and

[0568] The control unit controls the UL transmission based on the codebook.

[0569] The control unit controls the division of SRS transmission power based on the type of measurement reference signal resource, i.e., SRS resource, set in the codebook.

[0570] [Postscript 2]

[0571] The terminal as described in Appendix 1, wherein,

[0572] When a 4-port SRS resource is configured, the control unit divides the SRS transmission power toward the 4 ports among 3 of the 4 ports.

[0573] [Postscript 3]

[0574] The terminal as described in Appendix 1 or Appendix 2, wherein,

[0575] When a 1-port SRS resource or a 2-port SRS resource is configured in time division multiplexing (TDM) mode, the control unit divides the SRS transmission power between the ports that are transmitted in one symbol.

[0576] [Postscript 4]

[0577] The terminal as described in any one of Annexes 1 to 3, wherein,

[0578] When multiple SRS resources are configured in time division multiplexing (TDM) or frequency division multiplexing (FDM), the control unit divides the SRS transmission power between ports that are transmitted in one symbol or by the number of SRS resources.

[0579] (Postscript)

[0580] Regarding one embodiment of this disclosure (sixth / seventh embodiment), the following invention is noted.

[0581] [Postscript 1]

[0582] A terminal having:

[0583] The receiving unit receives a codebook transmitted via the uplink (UL) using three antenna ports (3TX); and

[0584] The control unit controls the UL transmission based on the codebook.

[0585] The control unit determines the transmission opportunity of the SRS resource based on the indication (SRI) for the measurement reference signal (SRS) resource set in the codebook.

[0586] [Postscript 2]

[0587] The terminal as described in Appendix 1, wherein,

[0588] The control unit determines the transmission opportunity based on specific additional conditions for the SRI.

[0589] [Postscript 3]

[0590] The terminal as described in Appendix 1 or Appendix 2, wherein,

[0591] If the specific additional conditions for the SRI are not met, the control unit applies specific discard rules to control the UL transmission.

[0592] [Postscript 4]

[0593] The terminal as described in any one of Annexes 1 to 3, wherein,

[0594] The control unit determines the quantity of SRS resources based on whether multiple transmit / receive points (MTRPs) are set to send repeatedly.

[0595] (Wireless communication system)

[0596] The structure of a wireless communication system according to one embodiment of this disclosure will be described below. In this wireless communication system, communication is performed using any one or a combination of the wireless communication methods according to the above embodiments of this disclosure.

[0597] Figure 16This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one implementation. The wireless communication system 1 (which may also be referred to simply as System 1) may also be a system that uses Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) as standardized by the Third Generation Partnership Project (3GPP).

[0598] Furthermore, the wireless communication system 1 can also support dual connectivity between multiple radio access technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC can also 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.

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

[0600] Wireless communication system 1 can also support dual connectivity between multiple base stations within the same RAT (e.g., MN and SN are dual connectivity between NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

[0601] The wireless communication system 1 may also include: a base station 11 forming a macro cell C1 with a relatively wide coverage area, and a base station 12 (12a-12c) configured within the macro cell C1 and forming a small cell C2 narrower than the macro cell C1. User terminals 20 may also be located within at least one cell. The configuration and number of each cell and user terminal 20 are not limited to the arrangement shown in the figure. Hereinafter, without distinguishing between base stations 11 and 12, they will be collectively referred to as base station 10.

[0602] User terminal 20 may also be connected to at least one of multiple base stations 10. User terminal 20 may also utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0603] Each CC can also be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). Macro cell C1 can also be included in FR1, and small cell C2 can also be included in FR2. For example, FR1 can also be a frequency band below 6 GHz (sub-6 GHz), and FR2 can also be a frequency band above 24 GHz (above-24 GHz). In addition, the frequency bands and definitions of FR1 and FR2 are not limited to these; for example, FR1 can also be equivalent to a frequency band higher than FR2.

[0604] In addition, in each CC, user terminal 20 can also use at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) for communication.

[0605] Multiple base stations 10 can also be connected via wired (e.g., fiber optic cable based on the Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (e.g., NR communication). For example, when NR communication between base stations 11 and 12 is used as a backhaul, base station 11, which is equivalent to a host station, can also be referred to as an Integrated Access Backhaul (IAB) donor, and base station 12, which is equivalent to a relay station, can also be referred to as an IAB node.

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

[0607] The core network 30 may also include, for example, user plane functions (UPF), access and mobility management functions (AMF), session management functions (SMF), unified data management (UDM), application functions (AF), data network (DN), location management functions (LMF), and network functions (NF) such as operation, administration and maintenance (OAM). Alternatively, a single network node may provide multiple functions. Furthermore, communication with external networks (e.g., the Internet) can also be conducted via the DN.

[0608] User terminal 20 can also be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0609] In wireless communication system 1, wireless access methods based on Orthogonal Frequency Division Multiplexing (OFDM) can also be used. For example, in at least one of the downlink (DL) and uplink (UL) links, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA) can also be used.

[0610] Wireless access methods can also be referred to as waveforms. In addition, in wireless communication system 1, other wireless access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) can also be applied in the wireless access methods of UL and DL.

[0611] As a downlink channel, the wireless communication system 1 can also use downlink shared channels (Physical Downlink Shared Channel (PDSCH)), broadcast channels (Physical Broadcast Channel (PBCH)), downlink control channels (Physical Downlink Control Channel (PDCCH)) and so on, which are shared among the user terminals 20.

[0612] In addition, as uplink channels, the wireless communication system 1 may also use uplink shared channels (Physical Uplink Shared Channel (PUSCH)), uplink control channels (Physical Uplink Control Channel (PUCCH)), random access channels (Physical Random Access Channel (PRACH)) and so on, which are shared by each user terminal 20.

[0613] User data, high-level control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and high-level control information can also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) can be transmitted via PBCH.

[0614] Lower-layer control information can also be transmitted via PDCCH. This lower-layer control information may include, for example, downlink control information (DCI), which includes scheduling information for at least one of PDSCH and PUSCH.

[0615] Additionally, the DCI for scheduling PDSCH can also be called DL allocation, DL DCI, etc., and the DCI for scheduling PUSCH can also be called UL authorization, UL DCI, etc. Furthermore, PDSCH can be rewritten as DL data, and PUSCH can be rewritten as UL data.

[0616] In PDCCH detection, a Control Resource Set (CORESET) and a search space can also be utilized. A CORESET corresponds to the resources used to search for DCIs. The search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor CORESETs associated with a specific search space based on search space settings.

[0617] A search space can also correspond to a PDCCH candidate that matches one or more aggregation levels. One or more search spaces can also be referred to as a search space set. In addition, the terms "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting" etc. disclosed herein can be rewritten interchangeably.

[0618] Uplink control information (UCI) can also be transmitted via PUCCH, including at least one of the following: Channel State Information (CSI), delivery confirmation information (e.g., also known as Hybrid Automatic Repeat reQuest ACK knowledgement (HARQ-ACK), ACK / NACK, etc.), and Scheduling Request (SR). Random access preambles used for establishing a connection with the cell can also be transmitted via PRACH.

[0619] In addition, in this disclosure, downlink, uplink, etc., may be described without the word "link". Furthermore, various channels may be described without the word "physical".

[0620] In wireless communication system 1, synchronization signals (SS) and downlink reference signals (DL-RS) can also be transmitted. In wireless communication system 1, as DL-RS, cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), positioning reference signals (PRS), and phase tracking reference signals (PTRS) can also be transmitted.

[0621] Synchronization signals can be, for example, at least one of the primary synchronization signal (PSS) and the secondary synchronization signal (SSS). A signal block containing SS (PSS, SSS) and PBCH (and DMRS for PBCH) can also be called an SS / PBCH block, SS block (SSB), etc. In addition, SS, SSB, etc. can also be called reference signals.

[0622] Furthermore, in wireless communication system 1, the uplink reference signal (UL-RS) can also transmit measurement reference signals (sounding reference signals (SRS)) and demodulation reference signals (DMRS). Additionally, DMRS can also be referred to as user terminal-specific reference signals (UE-specific reference signals).

[0623] (Base station)

[0624] Figure 17 This diagram illustrates an example of the structure of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmit / receive unit 120, a transmit / receive antenna 130, and a transmission path interface (transmission line interface) 140. Alternatively, the control unit 110, the transmit / receive unit 120, the transmit / receive antenna 130, and the transmission path interface 140 may each be provided in more than one manner.

[0625] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the base station 10 may also possess other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0626] The control unit 110 performs overall control of the base station 10. The control unit 110 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the art to which this disclosure pertains.

[0627] The control unit 110 can also control signal generation and scheduling (e.g., resource allocation, mapping). The control unit 110 can also control transmission, reception, and measurement using the transmit / receive unit 120, transmit / receive antenna 130, and transmission path interface 140. The control unit 110 can also generate data, control information, sequences, etc., to be transmitted as signals and forward them to the transmit / receive unit 120. The control unit 110 can also perform call processing (setting, releasing, etc.) of the communication channel, status management of the base station 10, and management of wireless resources.

[0628] The transmitting / receiving unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may also include a transmitting processing unit 1211 and a receiving processing unit 1212. The transmitting / receiving unit 120 may be composed of a transmitter / receiver, RF circuitry, baseband circuitry, filters, phase shifters, measurement circuitry, transmitting / receiving circuitry, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0629] The transmitting and receiving unit 120 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 1211 and an RF unit 122. The receiving unit can also be composed of a receiving processing unit 1212, an RF unit 122, and a measurement unit 123.

[0630] The transmitting and receiving antenna 130 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

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

[0632] The transmitting and receiving unit 120 may also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc., to form at least one of the transmitting beam and the receiving beam.

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

[0634] The transmitting and receiving unit 120 (transmitting processing unit 1211) can also perform transmission processing such as channel coding (which may also include error correction coding), modulation, mapping, filter processing, Discrete Fourier Transform (DFT) processing (as needed), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output the baseband signal.

[0635] For baseband signals, the transmitting and receiving unit 120 (RF unit 122) can also perform modulation, filtering, amplification, etc., to the wireless frequency band, and transmit the wireless frequency band signals through the transmitting and receiving antenna 130.

[0636] On the other hand, the transmitting and receiving unit 120 (RF unit 122) can also amplify, filter, demodulate baseband signals, etc., for signals in the wireless frequency band that are received by the transmitting and receiving antenna 130.

[0637] For the acquired baseband signal, the transmitting and receiving unit 120 (receiving and processing unit 1212) can also perform receiving and processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to acquire user data.

[0638] The transmitting / receiving unit 120 (measurement unit 123) can also perform measurements related to the received signal. For example, the measurement unit 123 can also perform radio resource management (RRM) measurements, channel state information (CSI) measurements, etc., based on the received signal. The measurement unit 123 can also 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 can also be output to the control unit 110.

[0639] The transmission path interface 140 can also transmit and receive signals (backhaul signaling) between the device included in the core network 30 (e.g., the network node providing the NF), other base stations 10, etc., and can also acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0640] In addition, the transmitting unit and receiving unit of the base station 10 in this disclosure may also be composed of at least one of the transmitting and receiving unit 120, the transmitting and receiving antenna 130 and the transmission path interface 140.

[0641] The transmit / receive unit 120 can send a codebook for uplink (UL) transmission using three antenna ports (3TX) to the terminal. The control unit 110 can control the reception of the UL transmission from the terminal based on the codebook. The control unit 110 can control the division of SRS transmit power based on the type of measurement reference signal (SRS) resource set in the codebook.

[0642] The control unit 110 can set the transmission opportunity of the SRS resource associated with the indication (SRI) of the measurement reference signal (SRS) resource set in the codebook.

[0643] (User terminal)

[0644] Figure 18 This diagram illustrates an example of the structure of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Alternatively, more than one of each of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be included.

[0645] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the user terminal 20 may also possess other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0646] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the art to which this disclosure pertains.

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

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

[0649] The transmitting and receiving unit 220 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 2211 and an RF unit 222. The receiving unit can also be composed of a receiving processing unit 2212, an RF unit 222, and a measurement unit 223.

[0650] The transmitting and receiving antenna 230 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0651] The transmitting / receiving unit 220 can also receive the downlink channel, synchronization signal, downlink reference signal, etc., mentioned above. The transmitting / receiving unit 220 can also transmit the uplink channel, uplink reference signal, etc., mentioned above.

[0652] The transmitting and receiving unit 220 may also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc., to form at least one of the transmitting beam and the receiving beam.

[0653] The transmitting and receiving unit 220 (transmitting processing unit 2211) may, for example, perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control) on the data and control information obtained from the control unit 210, and generate the bit string to be transmitted.

[0654] The transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform channel coding (which may include error correction coding), modulation, mapping, filter processing, DFT processing (as needed), IFFT processing, precoding, digital-to-analog conversion and other transmission processing on the bit string to be transmitted, and output the baseband signal.

[0655] Furthermore, whether or not to apply DFT processing can be based on the transform precoding settings. For a certain channel (e.g., PUSCH), if transform precoding is activated, the transmit / receive unit 220 (transmit processing unit 2211) can perform DFT processing as described above in order to transmit the channel using the DFT-s-OFDM waveform. If not, the transmit / receive unit 220 (transmit processing unit 2211) can perform the above transmission processing without performing DFT processing.

[0656] The transmitting and receiving unit 220 (RF unit 222) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 230.

[0657] On the other hand, the transmitting and receiving unit 220 (RF unit 222) can also amplify, filter, demodulate, etc., the signals of the wireless frequency band received by the transmitting and receiving antenna 230.

[0658] The transmitting and receiving unit 220 (receiving and processing unit 2212) can also perform receiving and processing on the acquired baseband signal, such as analog-to-digital conversion, FFT processing, IDFT processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to obtain user data.

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

[0660] Additionally, the measurement unit 223 can also derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources can be, for example, non-zero power (NZP) CSI-RS resources. Furthermore, the measurement unit 223 can also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources can be at least one of NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. Additionally, CSI-IM can also be referred to as CSI-Interference Management (IM), and can be interchanged with zero power (ZP) CSI-RS. Furthermore, in this disclosure, CSI-RS, NZPCSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., can also be interchanged.

[0661] Alternatively, the transmitting and receiving units of the user terminal 20 in this disclosure may also be composed of at least one of the transmitting and receiving unit 220 and the transmitting and receiving antenna 230.

[0662] The transmit / receive unit 220 can receive a codebook for uplink (UL) transmission using three antenna ports (3TX). The control unit 210 can control the UL transmission based on the codebook. The control unit 210 can control the division of SRS transmission power based on the type of Measurement Reference Signal (SRS) resources set in the codebook. When a 4-port SRS resource is set, the control unit 210 can divide the 4-port SRS transmission power among three of the four ports. When a 1-port or 2-port SRS resource is set in Time Division Multiplexing (TDM), the control unit 210 can divide the SRS transmission power among the ports transmitted in one symbol. When multiple SRS resources are set in Time Division Multiplexing (TDM) or Frequency Division Multiplexing (FDM), the control unit 210 can divide the SRS transmission power among the ports transmitted in one symbol or by the number of SRS resources.

[0663] The control unit 210 determines the transmission opportunity of the SRS resource based on the indication (SRI) for the Measurement Reference Signal (SRS) resource set in the codebook. The control unit 210 determines the transmission opportunity based on specific additional conditions for the SRI. If the specific additional conditions for the SRI are not met, the control unit 210 can apply specific discard rules to control the UL transmission. The control unit 210 determines the quantity of the SRS resource based on whether repeated transmissions by multiple transmit / receive points (MTRPs) are configured.

[0664] (Hardware structure)

[0665] Furthermore, the block diagrams used in the description of the above embodiments illustrate functional units. These functional blocks (structural units) are implemented through any combination of at least one of hardware and software. Moreover, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented using a single device that is physically or logically combined, or it can be implemented by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. A functional block can also be implemented by combining the aforementioned single device or multiple devices with software.

[0666] Here, the functions include judgment, decision, determination, calculation, calculation, processing, export, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, regard as, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, a functional block (structural unit) that implements the sending function can also be called a transmitting unit, transmitter, etc. As described above, the implementation method is not particularly limited.

[0667] For example, in one embodiment of this disclosure, the base station, user terminal, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 19This diagram illustrates an example of the hardware structure of a base station and a user terminal according to one embodiment. The base station 10 and the user terminal 20 described above can also be physically configured as a computer device including a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0668] Furthermore, in this disclosure, terms such as apparatus, circuit, device, section, and unit can be interchanged. The hardware structure of base station 10 and user terminal 20 can be configured to include one or more of the apparatuses shown in the figures, or it can be configured not to include any of the apparatuses.

[0669] For example, only one processor 1001 is shown, but there can be multiple processors. Furthermore, processing can be performed by one processor, or simultaneously, sequentially, or by two or more processors using other methods. Additionally, processor 1001 can be implemented using more than one chip.

[0670] The functions of the base station 10 and the user terminal 20 are implemented, for example, by reading specific software (programs) into hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs calculations and controls communication via the communication device 1004, or controls at least one of reading out and writing data in the memory 1002 and the storage device 1003.

[0671] The processor 1001, for example, enables the operating system to operate and control the computer as a whole. The processor 1001 may also be configured as a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic devices, registers, etc. For example, at least some of the control unit 110 (210), the transmit / receive unit 120 (220), etc. described above may also be implemented by the processor 1001.

[0672] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and performs various processes accordingly. As a program, a program that causes the computer to perform at least a portion of the operations described in the above embodiments can be used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and operated in the processor 1001; similar implementations can be made for other functional blocks.

[0673] The memory 1002 may also be a computer-readable recording medium, such as being composed of at least one of read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), random access memory (RAM), or other suitable storage media. The memory 1002 may also be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 is capable of storing executable programs (program code), software modules, etc., for implementing the wireless communication method according to one embodiment of this disclosure.

[0674] Storage device 1003 may also be a computer-readable recording medium, such as at least one of a flexible disc, floppy disk, optical disk (e.g., compact disc ROM, CD-ROM), digital multifunction disk, Blu-ray disc, removable disk, hard disk drive, smart card, flash memory device (e.g., card, stick, key drive), stripe, database, server, or other suitable storage medium. Storage device 1003 may also be referred to as an auxiliary storage device.

[0675] The communication device 1004 is hardware (transmitting and receiving device) used for communication between computers via at least one of a wired network and a wireless network. It is also referred to as a network device, network controller, network interface card (NIC), communication module, etc. To implement at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD), the communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the aforementioned transmitting and receiving unit 120 (220) and transmitting and receiving antenna 130 (230) can also be implemented by the communication device 1004. The transmitting and receiving unit 120 (220) can also be implemented by physically or logically separating the transmitting unit 120a (220a) and the receiving unit 120b (220b).

[0676] Input device 1005 is an input device that receives input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, light-emitting diode (LED) lamp, etc.). Alternatively, input device 1005 and output device 1006 can also be an integrated structure (e.g., a touch panel).

[0677] Furthermore, the processor 1001, memory 1002, and other devices are connected via a bus 1007 for communicating information. The bus 1007 can be configured as a single bus or as different buses between the devices.

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

[0679] (Variation example)

[0680] Furthermore, the terms described in this disclosure, as well as those necessary for understanding this disclosure, may be replaced with terms that have the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be interchanged. Additionally, a signal may also be a message. A reference signal can also be abbreviated as RS, and may be referred to as pilot, pilot signal, etc., depending on the applied standard. Furthermore, a component carrier (CC) may also be referred to as cell, frequency carrier, carrier frequency, etc.

[0681] A radio frame can also be composed of one or more periods (frames) in the time domain. Each of these periods (frames) that constitutes a radio frame can also be called a subframe. Furthermore, a subframe can also be composed of one or more time slots in the time domain. A subframe can also be a fixed time length (e.g., 1 ms) independent of the parameter set (numerology).

[0682] Here, the parameter set can also refer to communication parameters applied in at least one of the transmission and reception of a signal or channel. For example, the parameter set can also represent at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transmitter and receiver in the frequency domain, and specific windowing processing performed by the transmitter and receiver in the time domain.

[0683] In the time domain, a time slot can also be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.). In addition, a time slot can also be a time unit based on a set of parameters.

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

[0685] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can also use their respective other names. Furthermore, the time units such as frames, subframes, time slots, mini-time slots, and symbols in this disclosure can be interchanged.

[0686] For example, a subframe can also be called a TTI, multiple consecutive subframes can also be called a TTI, and a time slot or a mini-time slot can also be called a TTI. That is to say, at least one of the subframe and TTI can be a subframe in the existing LTE (1ms), a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but a time slot, mini-time slot, etc.

[0687] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules radio resources (frequency bandwidth, transmit power, etc., available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0688] TTI can also be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., and can also be a unit of processing such as scheduling and link adaptation. In addition, when a TTI is given, the actual time interval (e.g., the number of symbols) mapped to transmission blocks, code blocks, codewords, etc. can be shorter than the TTI.

[0689] Additionally, where a time slot or a mini-time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can also serve as the minimum time unit for scheduling. Furthermore, the number of time slots (mini-time slots) constituting the minimum time unit of the schedule can also be controlled.

[0690] A TTI with a duration of 1 ms can also be referred to as a normal TTI (TTI in 3GPP Rel.8-12), a standard TTI, a long TTI, a normal subframe, a standard subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI can also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini time slot, a sub-time slot, a time slot, etc.

[0691] In addition, long TTIs (e.g., normal TTIs, subframes, etc.) can be replaced with TTIs with a duration of more than 1ms, and short TTIs (e.g., shortened TTIs, etc.) can be replaced with TTIs with a duration of less than long TTIs but more than 1ms.

[0692] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can also contain one or more consecutive subcarriers. The number of subcarriers in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers in an RB can also be determined based on the parameter set.

[0693] Furthermore, an RB can contain one or more symbols in the time domain, and can also be a time slot, a mini-time slot, a subframe, or the length of a TTI. A TTI, a subframe, etc., can also be composed of one or more resource blocks.

[0694] In addition, one or more RBs can also be referred to as Physical Resource Blocks (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0695] In addition, a resource block can also consist of one or more resource elements (REs). For example, an RE can also be a radio resource area consisting of a subcarrier and a symbol.

[0696] The Bandwidth Part (BWP) (also referred to as partial bandwidth, etc.) can also represent a subset of consecutive common resource blocks (RBs) used for a certain parameter set in a certain carrier. Here, common RBs can also be determined by the index of RBs based on the common reference point of the carrier. PRBs can also be defined in a BWP and appended with numbers within that BWP.

[0697] A BWP can also include a UL BWP (the BWP used by UL) and a DL BWP (the BWP used by DL). For a UE, one or more BWPs can also be set within a single carrier.

[0698] At least one of the configured BWPs can be active, and the UE may not intend to transmit or receive specific signals / channels outside of the active BWPs. Furthermore, the terms "cell," "carrier," etc., in this disclosure can be rewritten as "BWP."

[0699] Furthermore, the structures described above, such as radio frames, subframes, time slots, mini-time slots, and symbols, are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained within a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, and the number of symbols in a TTI, symbol length, and cyclic prefix (CP) length can be varied in many ways.

[0700] Furthermore, the information, parameters, etc., described in this disclosure can be represented by absolute values, relative values ​​with respect to a specific value, or other corresponding information. For example, wireless resources can also be indicated by a specific index.

[0701] In this disclosure, the names used for parameters, etc., are not limiting names in any respect. Furthermore, the mathematical expressions, etc., using these parameters may differ from those explicitly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name; therefore, the various names assigned to these various channels and information elements are not limiting names in any respect.

[0702] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be mentioned throughout the above description, can also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[0703] Furthermore, information, signals, etc., can be output in at least one of the following directions: from higher level (upper layer) to lower level (lower layer), and from lower layer to higher level. Information, signals, etc., can also be input and output via multiple network nodes.

[0704] Input and output information, signals, etc., can be stored in a specific location (e.g., memory) or managed using management tables. Input and output information, signals, etc., can be overwritten, updated, or appended. Output information, signals, etc., can also be deleted. Input information, signals, etc., can also be sent to other devices.

[0705] The notification of information is not limited to the methods / implementations described in this disclosure, and may also be carried out by other methods. For example, the notification of information in this disclosure may also be implemented by physical layer signaling (e.g., downlink control information (DCI), uplink control information (UCI), etc.), higher layer signaling (e.g., radio resource control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB) etc.), medium access control (MAC) signaling), other signals, or combinations thereof.

[0706] In addition, physical layer signaling can also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. Furthermore, RRC signaling can also be referred to as RRC messages, such as RRC connection setup messages, RRC connection reconfiguration messages, etc. Additionally, MAC signaling can also be notified using, for example, the MAC control element (CE).

[0707] Furthermore, notification of specific information (e.g., a notification of “is X”) is not limited to explicit notification, but can also be implicit (e.g., by not providing that specific information, or by providing other information).

[0708] The determination can be made by a value represented by a single bit (0 or 1), by a true or false value (boolean), or by a numerical comparison (e.g., a comparison with a specific value).

[0709] Whether it is called software, firmware, middleware, microcode, hardware description language, or any other name, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, program, subprogram, software module, application, software application, software package, routine, subroutine, object, executable file, execution thread, process, function, etc.

[0710] Furthermore, software, instructions, and information can also be sent and received via a transmission medium. For example, when software is sent from a website, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL) etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of a transmission medium.

[0711] The terms “system” and “network” as used in this disclosure are interchangeable. “Network” may also mean devices included in a network (e.g., base stations).

[0712] In this disclosure, the terms “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 amplitude”, “beam angle”, “antenna”, “antenna element”, “panel”, “UE panel”, “transmitting entity”, and “receiving entity” are used interchangeably.

[0713] Furthermore, in this disclosure, the antenna port and the antenna port used for any signal / channel (e.g., the DeModulation Reference Signal (DMRS) port) can be mutually modified. In this disclosure, the resources and the resources used for any signal / channel (e.g., reference signal resources, SRS resources, etc.) can also be mutually modified. Additionally, resources may also include time / frequency / symbol / space / power resources. Moreover, the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0714] The aforementioned groups may include, for example, at least one of the following: spatial relation group, code division multiplexing (CDM) group, reference signal (RS) group, control resource set (CORESET) group, PUCCH group, antenna port group (e.g., DMRS port group), layer group, resource group, beam group, antenna group, panel group, etc.

[0715] Furthermore, in this disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET Pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), RS, etc., can also be rewritten to each other.

[0716] Furthermore, in this disclosure, the TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, and joint TCI state can also be rewritten to each other.

[0717] Furthermore, in this disclosure, terms such as "QCL", "QCL concept", "QCL relationship", "QCL type information", "QCL property (QCLproperty / properties)", "specific QCL type (e.g., type A, type D) property", and "specific QCL type (e.g., type A, type D)" can be rewritten interchangeably.

[0718] In this disclosure, indexes, identifiers (IDs), indicators, indications, resource IDs, etc., can be interchanged. Sequences, lists, sets, groups, clusters, subsets, etc., can also be interchanged.

[0719] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) can be interchanged. "Spatial relationship information (TCI state)" and "a set of spatial relationship information (TCI states)," or "one or more spatial relationship information," can also be interchanged. TCI state and TCI can also be interchanged. Spatial relationship information and spatial relationship can also be interchanged.

[0720] In this disclosure, the terms "Base Station (BS)", "Wireless Base Station", "Fixed Station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "Access Point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "Panel", "Cell", "Sector", "Cell Group", "Carrier", and "Component Carrier" are used interchangeably. There are also instances where terms such as macro cell, small cell, femtocell, and picocell are used to refer to base stations.

[0721] 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, each of which can also provide communication services through a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​the base station providing communication services within that coverage area, as well as at least one of the base station subsystems.

[0722] In this disclosure, the information sent by the base station to the terminal and the control / operation instructed by the base station to the terminal based on that information can also be rewritten.

[0723] In this disclosure, the terms “Mobile Station (MS)”, “user terminal”, “user equipment (UE)”, and “terminal” are used interchangeably.

[0724] There are also instances where mobile stations are referred to as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or several other appropriate terms.

[0725] At least one of the base station and the mobile station can also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. Additionally, at least one of the base station and the mobile station can also be a device mounted on a moving object, the moving object itself, etc.

[0726] The term "mobile body" refers to a movable object whose speed is arbitrary, including situations where the body is stationary. Examples of such mobile bodies include vehicles, transport vehicles, automobiles, autonomous two-wheelers, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, trailers, rickshaws, ships (bottles and other watercraft), airplanes, rockets, artificial satellites, drones, multi-rotor aircraft, quadcopters, balloons, and objects carried on them, but are not limited to these. Furthermore, the mobile body can also be a mobile body that moves autonomously based on operational commands.

[0727] The mobile entity can be a means of transportation (e.g., a vehicle, an airplane, etc.), a mobile entity moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Additionally, at least one of the base station and the mobile station may include a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may also be an IoT (Internet of Things) device such as a sensor.

[0728] Figure 20 This figure illustrates an example of a vehicle according to one embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a gear shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a speed 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 gear shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[0729] The drive unit 41 is comprised of at least one of an engine, a motor, or a combination of an engine and a motor. The steering unit 42 is configured to include at least a steering wheel (also called a handlebar) and to perform directional control on at least one of the front wheel 46 and the rear wheel 47 based on the operation of the steering wheel by the user.

[0730] The electronic control unit 49 consists of a microprocessor 61, a memory (ROM, RAM) 62, and a communication port (e.g., an input / output (IO) port) 63). Signals from various sensors 50-58 present in the vehicle are input into the electronic control unit 49. The electronic control unit 49 can also be referred to as an electronic control unit (ECU).

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

[0732] The information service unit 59 comprises various devices such as a car navigation system, audio system, speakers, display, television, and radio, used to provide (output) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The information service unit 59 uses information obtained from external devices via the communication module 60, etc., to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

[0733] The information service unit 59 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) or output devices that implement output to the outside (e.g., display, speaker, LED light, touch panel, etc.).

[0734] The driver assistance system unit 64 comprises various devices used to provide functions for preventing accidents or reducing the driver's workload, such as millimeter-wave radar, light detection and ranging (LiDAR), cameras, positioning devices (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) mapping), gyroscope systems (e.g., Inertial Measurement Unit (IMU)) and Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, and one or more ECUs that control these devices. Furthermore, the driver assistance system unit 64 sends and receives various information via communication module 60 to realize driver assistance or autonomous driving functions.

[0735] The communication module 60 can communicate with the microprocessor 61 and the constituent elements of the vehicle 40 via the communication port 63. For example, the communication module 60 sends and receives data (information) between the microprocessor 61 and the memory (ROM, RAM) 62, and various sensors 50-58 in the drive unit 41, steering control unit 42, accelerator pedal 43, brake pedal 44, gear shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, electronic control unit 49, and the vehicle 40 via the communication port 63.

[0736] The communication module 60 is controlled by the microprocessor 61 of the electronic control unit 49 and is a communication device capable of communicating with external devices. For example, it can transmit and receive various types of information between external devices via wireless communication. The communication module 60 can be located either inside or outside the electronic control unit 49. The external device can be, for example, the aforementioned base station 10, user terminal 20, etc. Furthermore, the communication module 60 can be, for example, at least one of the aforementioned base station 10 and user terminal 20 (or it can function as at least one of the base station 10 and user terminal 20).

[0737] The communication module 60 can also wirelessly transmit to an external device at least one of the signals input to the electronic control unit 49 from the various sensors 50-58, information obtained based on those signals, and information based on input from an external source (user) obtained via the information service unit 59. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc., can also be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 60 can also contain information based on the aforementioned inputs.

[0738] The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) sent from external devices and displays it to the information service unit 59 provided by the vehicle. The information service unit 59 can also be referred to as an information output unit (e.g., outputting information to devices such as displays and speakers based on the PDSCH received by the communication module 60 (or the data / information decoded from the PDSCH)).

[0739] Furthermore, the communication module 60 stores various information received from external devices into a memory 62 that can be utilized by the microprocessor 61. The microprocessor 61 can also control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, gear shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, and various sensors 50-58 of the vehicle 40 based on the information stored in the memory 62.

[0740] Furthermore, the base station in this disclosure can also be replaced by a user terminal. For example, various methods / implementations of this disclosure can be applied to structures where communication between the base station and the user terminal is replaced by communication between multiple user terminals (e.g., also referred to as device-to-device (D2D) or vehicle-to-everything (V2X)). In this case, it can also be configured such that the user terminal 20 has the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can be rewritten as terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can also be rewritten as sidelink channel.

[0741] Similarly, the user terminal in this disclosure can also be rewritten as a base station. In this case, it can also be configured such that the base station 10 has the functions of the user terminal 20 described above.

[0742] In this disclosure, actions are assumed to be performed by the base station, and sometimes, depending on the circumstances, by its upper node. Clearly, in a network containing one or more network nodes having a base station, various operations performed for communication with a terminal can be performed by the base station, one or more network nodes other than the base station (e.g., considering a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc., but not limited to these), or combinations thereof.

[0743] The various methods / implementations described in this disclosure can be used individually, in combination, or switched as needed during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of the various methods / implementations described in this disclosure can be rearranged as long as they do not contradict each other. For example, with respect to the method described in this disclosure, the illustrated order is used to indicate various steps, but the order in which they are indicated is not limited.

[0744] The various methods / implementations described in this disclosure can also be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Futuregeneration radio access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE This includes 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-Wideband (UWB)), Bluetooth (registered trademark), systems utilizing other appropriate wireless communication methods, and next-generation systems extended, modified, established, or specified based on them. Furthermore, multiple systems can be combined (e.g., LTE or LTE-A, combinations with 5G, etc.) for application.

[0745] As used in this disclosure, the word "based on" does not mean "based on only" unless otherwise specified. In other words, the word "based on" means both "based on only" and "based on at least".

[0746] Any reference to an element using the designations "first," "second," etc., as used in this disclosure does not comprehensively limit the quantity or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, references to the first and second elements do not imply that only two elements may be used, or that the first element must take precedence over the second element in some form.

[0747] The term "determining" as used in this disclosure can encompass a wide variety of actions. For example, "determining" can also refer to judging, calculating, computing, processing, deriving, investigating, looking up (search, inquiry) (e.g., searching in a table, database, or other data structure), and ascertaining.

[0748] In addition, "judgment (decision)" can also refer to receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, accessing (e.g., accessing data in memory), etc., as situations where "judgment (decision)" is performed.

[0749] Furthermore, "judgment (decision)" can also refer to situations where resolving, selecting, choosing, establishing, or comparing are considered as making a "judgment (decision)". In other words, "judgment (decision)" can also refer to certain actions as situations where a "judgment (decision)" is made. In this disclosure, "judgment (decision)" and the aforementioned operations can also be rewritten interchangeably.

[0750] Furthermore, in this disclosure, "determine / determining" can be interchanged with "assume / assuming," "expect / expecting," and "consider / considering." Additionally, in this disclosure, "not assuming to proceed..." and "assuming not to proceed..." can also be interchanged.

[0751] In this disclosure, "expect" and "be expected" can be rewritten interchangeably. For example, "expect(s)......" ("..." can also be expressed using a that clause, to infinitive, etc.) and "be expected......" can also be rewritten interchangeably. "does not expect......" and "be not expected......" can also be rewritten interchangeably. Furthermore, "An apparatus A is not expected......" and "Apparatus B other than apparatus A does not expect......" can also be rewritten interchangeably (for example, if apparatus A is a UE, apparatus B can also be a base station).

[0752] The term "maximum transmit power" as used in this disclosure can refer to the maximum value of the transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the rated UE maximum transmit power).

[0753] As used in this disclosure, the terms “connected,” “coupled,” or all variations thereof, refer to all direct or indirect connections or combinations between two or more elements, and can include cases where there is one or more intermediate elements between two mutually “connected” or “coupled” elements. The connections or combinations between elements can be physical, logical, or a combination thereof. For example, “connected” can also be rewritten as “access.”

[0754] In this disclosure, when two elements are connected, it is possible to use more than one wire, cable, printed electrical connection, etc., and to use electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, light (both visible and invisible) region as several non-limiting and non-inclusive examples, so that they are "connected" or "combined" with each other.

[0755] In this disclosure, the term "A is different from B" can also mean "A and B are different from each other". Additionally, this term can also mean "A and B are different from C respectively". Terms such as "separate" and "combined" can also be interpreted in the same way as "different".

[0756] When the terms "include," "including," and variations thereof are used in this disclosure, these terms, like the term "comprising," mean inclusive. Furthermore, the term "or" as used in this disclosure does not mean XOR.

[0757] In this disclosure, for example, in cases where articles are added through translation, such as a, an, and the in English, the disclosure may also include cases where the noun following these articles is in a plural form.

[0758] In this disclosure, expressions such as "below," "less than," "above," "more," and "equal to" can be rewritten interchangeably. Furthermore, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "fast," "slow," "wide," and "narrow," etc., are not limited to the positive, comparative, and superlative degrees, and can be rewritten interchangeably. Additionally, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "fast," "slow," "wide," and "narrow," when used as expressions with the prefix "i" (where i is any integer), are not limited to the positive, comparative, and superlative degrees, and can be rewritten interchangeably (for example, "highest" and "i-th highest" can also be rewritten interchangeably).

[0759] In this disclosure, "of", "for", "regarding", "related to", "associated with", etc., can also be rewritten interchangeably.

[0760] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "in response to A", "based on A", "during / while A", "before A", "at the same time as / on A", "after A", "since A", and "until A" can be rewritten interchangeably. Furthermore, A and B can be appropriately replaced with nouns, gerunds, or ordinary sentences depending on the context. Additionally, the time difference between A and B can be approximately 0 (immediately following or immediately preceding). Moreover, a time offset can be applied to the time A occurs. For example, "A" can also be rewritten interchangeably with "before / after the time offset of A". The time offset (e.g., more than one symbol / slot) can be predetermined or determined by the UE based on the information it is notified of.

[0761] In this disclosure, timing, moment, time, time instance, arbitrary time unit (e.g., time slot, sub-time slot, symbol, subframe), period, occasion, resource, etc., can also be overridden.

[0762] The inventions disclosed herein have been described in detail above. However, it will be apparent to those skilled in the art that the inventions disclosed herein are not limited to the embodiments described herein. The description herein is for illustrative purposes only and is not intended to limit the inventions disclosed herein in any way.

Claims

1. A terminal, comprising: The receiving unit receives the codebook used for uplink transmission (3TX UL) via the three antenna ports; and The control unit controls the UL transmission based on the codebook. The control unit determines the transmission opportunity of the SRS resource based on the indication (SRI) for the measurement reference signal resource (SRS resource) set in the codebook.

2. The terminal as described in claim 1, wherein, The control unit determines the transmission opportunity based on specific additional conditions for the SRI.

3. The terminal as described in claim 1, wherein, If the specific additional conditions for the SRI are not met, the control unit applies specific discard rules to control the UL transmission.

4. The terminal as described in claim 1, wherein, The control unit determines the quantity of SRS resources based on whether multiple transmit / receive points (MTRPs) are set to send repeatedly.

5. A wireless communication method for a terminal, comprising: Receive the codebook used for uplink transmission via the three antenna ports, i.e., 3TX UL transmission; and The UL transmission is controlled based on the codebook. The step of determining the transmission opportunity of the SRS resource based on the indication (SRI) of the measurement reference signal resource (SRS resource) set in the codebook.

6. A base station, comprising: The transmitting unit sends the codebook used for uplink transmission (3TX UL) using the three antenna ports to the terminal; and The control unit controls the reception of the UL transmitted from the terminal based on the codebook. The control unit sets the transmission opportunity for the SRS resource associated with the indication of the measurement reference signal resource (SRS resource) set in the codebook, i.e., the SRI.

Images