Terminal, wireless communication method, and base station

Abstract

A terminal according to an embodiment of the present disclosure has: a reception unit that receives a host layer parameter for uplink (UL) transmission utilizing three non-codebook based antenna ports (3TX); and a control unit that controls activation of the non-codebook based 3TX UL transmission on the basis of the host layer parameter.

Description

Terminal, Wireless Communication Method, and Base Station

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

[0002] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was specified for the purpose of achieving further high data rates, low latency, etc. (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) was specified for the purpose of further increasing capacity and enhancing performance of LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

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

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

[0005] Rel. 15 NR supports uplink (UL) Multi-Input Multi-Output (MIMO) transmission up to 4 layers. For future NRs, support for UL transmission with more than 4 layers is being considered to achieve higher spectral efficiency. For example, for Rel. 18 NR, up to 6 ranks of transmission using 6 antenna ports, and up to 6 or 8 ranks of transmission using 8 antenna ports are being considered.

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

[0007] Furthermore, non-coded book-based UL transmission for 3TX is also being considered.

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

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

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

[0011] According to one aspect of this disclosure, UL transmission can be appropriately controlled.

[0012] Figure 1 shows an example of a precoding matrix table W for single-layer (rank 1) transmission using four antenna ports when the transform precoder is disabled in Rel. 16 NR. Figure 2 shows an example of a precoding matrix table W for two-layer (rank 2) transmission using four antenna ports when the transform precoder is disabled in Rel. 16 NR. Figure 3 shows an example of a precoding matrix table W for three-layer (rank 3) transmission using four antenna ports when the transform precoder is disabled in Rel. 16 NR. Figure 4 shows an example of a precoding matrix table W for four-layer (rank 4) transmission using four antenna ports when the transform precoder is disabled in Rel. 16 NR. Figure 5A shows an example of a precoding matrix table W for single-layer (rank 1) transmission using two antenna ports in Rel. 16 NR. Figure 5B shows an example of a precoding matrix table W for four-layer (rank 4) transmission using four antenna ports when the transform precoder is disabled in Rel. Figure 16 shows an example of a table of precoding matrices W for 2-layer (rank 2) transmission using 2 antenna ports when transform precoding is disabled. Figure 6 shows an example of the correspondence between the field values ​​of precoding information and the number of layers, and the number of layers and TPMI in Rel. 16 NR. Figures 7A-7C show the SRI instruction or second SRI instruction during codebook-based PUSCH transmission in Rel. 17. Figure 8 shows an example of an antenna layout for 8 antenna ports. Figure 9 shows candidate precoding matrices W for each transmission rank using 3 antenna ports. Figures 10A to 10C show an example of a table (separate table) of precoding matrices W for 1-3 layer (rank 1-3) transmission using 3 antenna ports when transform precoding is disabled. Figure 11 shows an example of a table (joint table) of precoding matrices W for 1-3 layer (rank 1-3) transmission using 3 antenna ports when transform precoding is disabled.Figures 12A and 12B show an example of the correspondence between precoding information and layer number field values ​​and layer number and TPMI. Figure 13 shows an example of the correspondence between precoding information and layer number field values ​​and layer number and TPMI. Figures 14A to 14C show an example of the correspondence between PTRS and DMRS in the non-codebook-based 3TX UL transmission of this disclosure. Figures 15A to 15C show an example of the correspondence between PTRS and DMRS in the codebook-based 3TX UL transmission of this disclosure. Figures 16A to 16C show an example of the correspondence between PTRS and DMRS in the 3TX UL transmission of this disclosure. Figure 17 shows an example of the schematic configuration of a wireless communication system according to one embodiment. Figure 18 shows an example of the configuration of a base station according to one embodiment. Figure 19 shows an example of the configuration of a user terminal according to one embodiment. Figure 20 shows an example of the hardware configuration of a base station and user terminal according to one embodiment. Figure 21 shows an example of a vehicle according to one embodiment.

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

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

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

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

[0017] Here, the SRS resource type may be one of the following: Periodic SRS (P-SRS), Semi-Persistent SRS (SP-SRS), or Aperiodic CSI (A-SRS). The UE may transmit P-SRS and SP-SRS periodically (or periodically after activation), and A-SRS based on DCI's SRS requests.

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

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

[0020] SRS resource information may include SRS resource ID (SRS-ResourceId), number of SRS ports, SRS port number, transmit 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.), hopping-related information, SRS resource type, sequence ID, SRS spatial relationship information, etc.

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

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

[0023] In this disclosure, the terms SSB index, SSB resource ID, and SSB Resource Indicator (SSBRI) may be interpreted interchangeably. Similarly, the terms CSI-RS index, CSI-RS resource ID, and CSI-RS Resource Indicator (CRI) may be interpreted interchangeably. Furthermore, the terms SRS index, SRS resource ID, and SRI may be interpreted interchangeably.

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

[0025] If a UE sets spatial relationship information regarding an SRS resource with respect to an SSB or CSI-RS, it may transmit the SRS resource using 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. In this case, the UE may assume that the UE receive beam for the SSB or CSI-RS and the UE transmit beam for the SRS are the same.

[0026] If a UE sets up spatial relationship information regarding a certain SRS (target SRS) resource and another SRS (reference SRS), it may transmit the target SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter (spatial domain transmit filter) used for transmitting the reference SRS. In other words, in this case, the UE may assume that the UE transmit beam of the reference SRS and the UE transmit beam of the target SRS are the same.

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

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

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

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

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

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

[0033] Furthermore, the UE may be configured to use either codebook-based or non-codebook-based PUSCH transmission via a higher-layer parameter "txConfig" that indicates the transmission scheme. This parameter may indicate a value of "codebook" or "noncodebook".

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

[0035] (Determination of the PUSCH precoder in codebook (CB) based transmission) As described above, in the case of codebook (CB) based transmission, the UE may determine the precoder for PUSCH transmission based on SRI, TRI, TPMI, etc.

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

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

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

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

[0040] Note that the precoder type may be specified by any one of full coherent (fully coherent), partial coherent, and non coherent, or a combination of at least two of them (for example, it may be represented by parameters such as "fully and partial and non coherent", "partial and non coherent").

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

[0042] Full coherent may mean that all antenna ports used for transmission are synchronized (it may be expressed as being able to align phases, being able to perform phase control for each coherent antenna port, being able to appropriately apply a precoder to each coherent antenna port, etc.). Partial coherent may mean that some of the antenna ports used for transmission are synchronized, but the some ports and other ports are not synchronized. Non coherent may mean that each antenna port used for transmission cannot be synchronized.

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

[0044] In the present disclosure, the precoder type, coherence, PUSCH transmission coherence, coherent type, coherence type, codebook type, codebook subset, codebook subset type, etc. may be read as each other.

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

[0046] FIG. 1 is a diagram showing an example of the association between a codebook subset and a TPMI index. FIG. 1 corresponds to a table of precoding matrices W for single-layer (rank 1) transmission using four antenna ports when transform precoding (which may also be called a transform precoder) is invalid in Rel. 16 NR. In FIG. 1, the corresponding W is shown in ascending order of the TPMI index from left to right (the same applies to FIG. 2).

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

[0048] In Figure 1, if the codebook subset is fully, partially, and noncoherent, the UE is notified of a TPMI (TPMI index) from 0 to 27 for a single-layer transmission. If the codebook subset is partially and noncoherent, the UE is set to a TPMI from 0 to 11 for a single-layer transmission. If the codebook subset is noncoherent, the UE is set to a TPMI from 0 to 3 for a single-layer transmission.

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

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

[0051] According to Figure 2, the TPMIs that the UE is notified of for a 2-layer transmission are 0 to 21 (codebook subset is complete, partial, and noncoherent), 0 to 13 (codebook subset is partial and noncoherent), or 0 to 5 (codebook subset is noncoherent).

[0052] According to Figure 3, the TPMI notified to the UE for a 3-layer transmission is between 0 and 6 (codebook subset is complete, partial, and noncoherent), between 0 and 2 (codebook subset is partial and noncoherent), or 0 (codebook subset is noncoherent).

[0053] According to Figure 4, the TPMI notified to the UE for a 4-layer transmission is between 0 and 4 (codebook subset is complete, partial, and noncoherent), between 0 and 2 (codebook subset is partial and noncoherent), or 0 (codebook subset is noncoherent).

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

[0055] According to Figure 5A, the TPMI that the UE is notified of for a 2-port single-layer transmission is between 0 and 5 (with a complete, partial, and non-coherent codebook subset) or between 0 and 1 (with a non-coherent codebook subset). If the notified TPMI is between 0 and 1, a non-coherent precoder is applied. If the notified TPMI is between 2 and 5, a fully coherent precoder is applied.

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

[0057] A precoding matrix in which each column has exactly one non-zero element may be called a non-coherent codebook. A precoding matrix in which each column has a specific number of non-zero elements (greater than one, but not the total number of elements in the column) may be called a partially coherent codebook. A precoding matrix in which all elements in each column are non-zero may be called a fully coherent codebook.

[0058] Non-coherent codebooks and partially coherent codebooks may also be called antenna selection precoders, antenna port selection precoders, etc. For example, a non-coherent codebook (non-coherent precoder) may also be called a one-port selection precoder, a one-port port selection precoder, etc. A partially coherent codebook (partially coherent precoder) may also be called an x-port (x is an integer greater than 1) selection precoder, a port selection precoder for x ports, etc. A fully coherent codebook may also be called a non-antenna selection precoder, an all-port precoder, etc. In this disclosure, codebook, codebook subset, and precoder may be interpreted interchangeably.

[0059] In this disclosure, a partially coherent codebook may refer to a subset of codebooks (precoding matrices) corresponding to TPMIs specified by DCI for codebook-based transmission, where a UE with a partially coherent codebook subset (e.g., RRC parameter "codebookSubset" = "partialAndNonCoherent") is set, excluding the codebooks corresponding to TPMIs specified by a UE with a noncoherent codebook subset (e.g., RRC parameter "codebookSubset" = "nonCoherent") (i.e., for single-layer transmission with four antenna ports, the codebooks for TPMIs 4 through 11).

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

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

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

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

[0064] Figure 6 shows an example of the correspondence between the field values ​​of precoding information and layer number, and the layer number and TPMI in Rel. 16 NR. The correspondence in this example is for a 4-antenna port when the transform precoder is disabled, the maximum rank (maxRank) is set to 2, 3, or 4, and uplink full power transmission is not set, or is set to full power mode 2, or is set to full power, but is not limited to this. It should be obvious to those skilled in the art that the "bit fields mapped to the index" shown represent the field values ​​of precoding information and layer number.

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

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

[0067] Furthermore, the precoding information field may be 0 bits for non-codebook-based PUSCH. Also, the precoding information field may be 0 bits for codebook-based PUSCH with one antenna port.

[0068] (SRS settings for Codebook-based PUCH) Figure 7A shows the cases in Rel. 17 where ul-FullPowerTransmission is not set, or ul-FullPowerTransmission=fullpowerMode1, or ul-FullPowerTransmission=fullpowerMode2, or ul-FullPowerTransmission=fullpower and N SRS This figure shows the SRI instruction or second SRI instruction during codebook-based PUSCH transmission when =2. Figure 7B shows ul-FullPowerTransmission=fullpowerMode2 and N in Rel. 17. SRS This figure shows the SRI instruction or second SRI instruction for codebook-based PUSCH transmission when =3. Figure 7C shows ul-FullPowerTransmission=fullpowerMode2 and N in Rel. 17. SRS When = 4, the diagram shows an SRI instruction or a second SRI instruction for codebook-based PUSCH transmission.

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

[0070] The SRS resource indicator field, when the upper layer parameter txConfig = codebook, follows Figure 7A-7C, [log2(N SRS )] is a bit. N SRS This is the number of configured SRS resources in the SRS resource set, indicated by the SRS resource set indicator field (if it exists). Otherwise, N SRS This is the number of configured SRS resources associated with the usage of the higher-level parameter 'codeBook' within the SRS resource set configured by the higher-level parameter srs-ResourceSetToAddModList.

[0071] In codebook-based transmissions, PUSCH is scheduled or semi-fixed according to DCI format 0_0, DCI format 0_1, and DCI format 0_2. One or two SRS resource sets can be configured in SRS-ResourceSetToAddModList, which has the upper layer parameter usage "codebook" for SRS-ResourceSet. Alternatively, one or two SRS resource sets can be configured in srs-ResourceSetToAddModListDCI-0-2, which has the upper layer parameter usage "codebook" for SRS-ResourceSet.

[0072] In srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, when setting two SRS resource sets by setting the usage of the higher-layer parameter of SRS-ResourceSet to "codebook", one or two SRIs and one or two TPMIs are provided by two SRS resource instruction fields and two precoding information fields, respectively.

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

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

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

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

[0077] In a normal codebook-based PUSCH, one SRS resource set can be configured, each containing two SRS resources with the same number of ports. In the case of a codebook-based PUSCH iteration (for a multi-transmission / reception point (TRP)), two SRS resource sets, each containing the same number of SRS resources, may be configured. In the case of "fullpowerMode2" in the codebook-based configuration, one SRS resource set can be configured, containing SRS resources with the same or different number of ports.

[0078] (Transmission with more than 4 antenna ports) Rel. 15 / 16 NR supports uplink (UL) Multi Input Multi Output (MIMO) transmission up to 4 layers. For future wireless communication systems, support for UL transmission with more than 4 layers is being considered to achieve higher spectral efficiency. For example, for Rel. 18 NR, up to 6 ranks of transmission using 6 antenna ports, and up to 6 or 8 ranks of transmission using 8 antenna ports are being considered.

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

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

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

[0082] The UE may report supported antenna groups, antenna placement information, and coherence count as UE capability information. The UE may also configure coherence groups (e.g., the number of coherence groups, the number of ports included in each coherence group) through upper-layer signaling.

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

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

[0085] Furthermore, in UEs of Rel. 15 and Rel. 16, it is assumed that only one beam / panel is used for UL transmission at any given time. However, in Rel. 17 and later, in order to improve UL throughput and reliability, simultaneous UL transmission of multiple beams / panels (e.g., PUSCH transmission) is being considered for one or more TRPs. Note that simultaneous PUSCH transmission of multiple beams / panels may correspond to PUSCH transmission with more than 4 layers, or to PUSCH transmission with 4 or fewer layers.

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

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

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

[0089] Figure 9 shows candidate precoding matrices W for each transmission rank using three antenna ports. Figures 10A to 10C show an example of a table (separate table) of precoding matrices W for 1-3 layer (rank 1-3) transmission using three antenna ports when the transform precoder is disabled. Figure 11 shows an example of a table (joint table) of precoding matrices W for 1-3 layer (rank 1-3) transmission using three antenna ports when the transform precoder is disabled. In Figures 10 and 11, the TPMI index of the W column increases from left to right (e.g., 0-2). The same applies hereafter.

[0090] A non-coherent UL codebook for 3TX UE may be defined as shown in Figures 9 to 11.

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

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

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

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

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

[0096] <Bitfields for Codebooks for 3TX UE> Figures 12A and 12B show an example of the correspondence between the field values ​​of precoding information and the number of layers, and the number of layers and TPMI. Figure 12A corresponds to the separate table described in Figure 10, and Figure 12B corresponds to the single table described in Figure 11.

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

[0098] As shown in Figure 12A, if the codebook subset is noncoherent and the maximum rank (transmit rank) is 1, then bit field indices 0 to 2 (bit fields mapped to the index) correspond to TPMI = 0 to 2 in each layer. Bit field index 3 may be a reserved bit.

[0099] Furthermore, if the codebook subset is non-coherent and the maximum number of ranks is 2, bit field indices 0 to 2 correspond to (indicate) TPMI = 0 to 2 in one layer each, and bit field indices 3 to 5 correspond to TPMI = 0 to 2 in two layers each. Bit field indices 6 and 7 may be reserved bits.

[0100] Furthermore, if the codebook subset is noncoherent and the maximum number of ranks is 3, bit field indices 0 to 2 correspond to (indicate) TPMI = 0 to 2 in one layer each, bit field indices 3 to 5 correspond to TPMI = 0 to 2 in two layers each, and bit field index 6 corresponds to TPMI = 0 in three layers. Bit field index 7 may be a reserved bit.

[0101] As shown in Figure 12B, if the codebook subset is noncoherent and the maximum rank (transmit rank) is 1, then bit field indices 0 to 2 (bit fields mapped to the index) correspond to TPMI = 0 to 2 in each layer. Bit field index 3 may be a reserved bit.

[0102] Furthermore, if the codebook subset is noncoherent and the maximum number of ranks is 2, bit field indices 0 to 2 correspond to (indicate) TPMI = 0 to 2 in one layer each, and bit field indices 3 to 5 correspond to TPMI = 3 to 5 in two layers each. Bit field indices 6 and 7 may be reserved bits.

[0103] Furthermore, if the codebook subset is non-coherent and the maximum number of ranks is 3, bit field indices 0 to 2 correspond to (indicate) TPMI = 0 to 2 in one layer each, bit field indices 3 to 5 correspond to TPMI = 3 to 5 in two layers each, and bit field index 6 corresponds to TPMI = 6 in three layers. Bit field index 7 may be a reserved bit.

[0104] Thus, as shown in Figure 12, when the maximum rank number is 1, the number of bits required for TPMI instruction is 2 bits, and when the maximum rank number is 2 or 3, the number of bits required for TPMI instruction is 3 bits.

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

[0106] <Enabling the Codebook for 3TX UE> Figure 13 shows an example of the correspondence between the field values ​​of precoding information and the number of layers, and the number of layers and TPMI.

[0107] The above examples illustrate cases where the transform precoder is disabled, but are not limited to these. Depending on the UE capabilities, the transform precoder may be enabled / configured for 3TX UEs (e.g., maximum rank = 1).

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

[0109] As shown in Figure 13, a dedicated correspondence (table) may be defined depending on the case in which the transform precoder is effective, but the correspondence with a maximum rank of 1 shown in Figure 12 may also be referenced (repurposed).

[0110] Thus, as shown in Figure 13 (or Figure 12), when the transform precoder is enabled with a maximum rank of 1, the number of bits required for TPMI instruction is 2 bits.

[0111] Furthermore, whether UE (3TX UE) supports a transform precoder for a codebook-based PUSCH with rank number = 1 can be reported by signaling for UE capability.

[0112] (Analysis) In addition to 3-antenna port codebook-based (3TX codebook-based) UL transmission, 3-antenna port non-codebook-based (3TX non-codebook-based) UL transmission is also being considered.

[0113] Some of the 3TX codebook-based provisions may also apply to / extend to the 3TX non-codebook-based.

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

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

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

[0117] In other words, in STRP, if one PTRS port is configured, the [Code Point] value = 3 is not used (corresponding to Reserved), compared to the existing specification.

[0118] Furthermore, in non-code book-based UL transmission using 3TX UE, if two PTRS ports are configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the indication (PTRS-DMRS related field) showing the relationship between PTRS and DMRS in two DMRS ports sharing one PTRS port is as follows:

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

[0120] Thus, in STRP, when two PTRS ports are configured, the least significant bit (LSB) is not used compared to the existing specification. In other words, the PTRS-DMRS related field is reduced from two bits to one bit.

[0121] Furthermore, in the case of codebook-based MTRP PUSCH repeated transmission using 3TX UE, the instructions indicating the relationship between PTRS and DMRS (PTRS-DMRS related fields) are as follows:

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

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

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

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

[0126] When the maximum number of ranks is 2, one PTRS-DMRS related field is indicated. Then, with 2 bits, the MSB and LSB can each be applied to two TRPs.

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

[0128] If only one PTRS port is configured, the existing MTRP specifications may be applied to 3TX.

[0129] Thus, the UE behavior regarding the correspondence between PTRS and DMRS in non-codebook-based PUSCH may differ between 3TX UE and existing UE in the following respects: • STRP when one PTRS port is configured. • STRP when two PTRS ports are configured. • MTRP when two PTRS ports are configured.

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

[0131] Similarly, in non-codebook-based UL transmission, it is necessary to consider methods for enabling 3TX and clarify the corresponding UE behavior.

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

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

[0134] As described above, the various regulations for realizing 3TX are still not sufficiently clear. Without these clarifications, there is a risk that UL transmission using three antenna ports cannot be properly controlled.

[0135] Therefore, the present inventors focused on the existence of such cases and conceived the wireless communication method described herein.

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

[0137] (Various substitutions) In this disclosure, words enclosed in parentheses () may indicate an explanation of the preceding word (e.g., an explanation of spelling), a paraphrase, a specific example, or supplementary explanation. Also, in this disclosure, words enclosed in square brackets [] may be interpreted as part of the overall meaning of the text, or they may be interpreted as being excluded (ignored). Note that parentheses () and square brackets [] may be used for purposes / meanings other than those described above.

[0138] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0139] In this disclosure, terms such as notice, activate, deactivate, indicate (or specify), select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and capable of operating may be interpreted interchangeably.

[0140] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Elements (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.

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

[0142] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).

[0143] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).

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

[0145] In this disclosure, the terms used include: panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmit entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relationship, 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 relationship group, Code Division Multiplexing (CDM) group, Reference Signal group, CORESET group, Physical Uplink Control The following terms may be interchangeable: Channel (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, quasi-co-location (QCL), QCL assumption, etc.

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

[0147] This disclosure primarily describes 3TX, but the same principles may apply to 5TX, 6TX, 7TX, TX with 8 or more layers, TX with 4 or fewer layers, etc. In the following embodiments, "3" may be read as "n (where n is any integer)," in which case the number of layers / ports etc. described assuming a maximum value of "3" can be appropriately read by those skilled in the art assuming a maximum value of "n."

[0148] In this disclosure, "having the ability to..." may be interpreted as "supporting / reporting the ability to...".

[0149] In this disclosure, rank, transmission rank, number of layers, and number of antenna ports may be interpreted interchangeably. Also, the application of one codeword and the number of layers being four or less may be interpreted interchangeably. The application of two codewords and the number of layers being greater than four may be interpreted interchangeably.

[0150] In this disclosure, a table may be interpreted as one or more tables.

[0151] In this disclosure, the terms table, mapping, correspondence, association, and relationship may be interpreted interchangeably.

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

[0153] (Wireless Communication Method) The embodiments of this disclosure can be broadly classified as follows: • First embodiment: Higher layer signaling (RRC parameters) for enabling non-code book-based UL transmission for 3TX. • Second embodiment: Relationship between PTRS and DMRS in non-code book-based UL transmission for 3TX. Each embodiment will be described below based on these.

[0154] In this disclosure, each embodiment / option may be applied individually or in combination with others.

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

[0156] In this disclosure, the association between precoding information (TPMI) and layer count (TRI) and the index (precoding information field value) may be defined in Specification 2 for Multiplexing and channel coding (Multiplexing and channel coding / Downlink transport channels and control information / Downlink control information / DCI formats / DCI format 0_1). In this disclosure, the association, table D-x, TRI / TPMI instruction table, DCI instruction table, and precoding information table may be interchangeable.

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

[0158] In this disclosure, TPMI, TPMI field, and precoding information may be interpreted interchangeably.

[0159] In each of the following embodiments, the precoding matrix / precoder may mean a complete / partial / non-coherent precoder.

[0160] In each of the following embodiments, a number corresponding to a certain index (e.g., TPMI index, antenna port index) (e.g., 0, 1, 2, etc.) may be read as a number preceded by a # (e.g., #0, #1, #2, etc.).

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

[0162] The 3TX UL transmission described herein is applicable not only to single / multi-TRP pushes but also to repetitions of multi-TRP pushes of Rel. 17 or STxMP SFN / SDM pushes of Rel. 18.

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

[0164] In this disclosure, unless otherwise specified, 3TX UL transmission may mean non-codebook-based UL transmission. That is, 3TX UE may mean UE that supports non-codebook-based UL transmission for 3TX.

[0165] In this disclosure, "non-code book-based 3TX UL transmission" and "non-code book-based UL transmission for 3TX" may be interpreted interchangeably.

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

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

[0168] New RRC parameters may be provided not only for each SRS resource set, but also for each BWP / CC / cell.

[0169] If two SRS resource sets are configured with the use case set to non-codebook (i.e., MTRP), the UE may expect the new RRC parameters described above to be set the same for both SRS resource sets.

[0170] In other words, in this case, the UE can assume / expect that the settings for enabling non-codebook-based UL transmission for 3TX are the same for the two SRS resource sets.

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

[0172] The above content may be extended and applied not only to non-codebook-based UL transmissions but also to codebook-based UL transmissions. In other words, the phrase "purpose is non-codebook (nonCodebook: NCB)" above may be read as "purpose is codebook (Codebook: CB)".

[0173] In other words, if two SRS resource sets are configured for use as defined in the codebook (i.e., MTRP), the UE may expect the RRC parameter that enables 3TX UL transmission (in which case one port of the 4-port SRS (e.g., port 1003) is muted) to be set the same for both SRS resource sets.

[0174] In other words, in this case, the UE can assume / expect that the settings for enabling codebook-based UL transmission for 3TX are the same for the two SRS resource sets.

[0175] This embodiment clarifies a method for enabling non-coded book-based UL transmission for 3TX. Based on this method, the UE can appropriately support operations related to non-coded book-based UL transmission for 3TX.

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

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

[0178] The phrase "when 3TX UL transmission is enabled by a new RRC parameter in a non-code book-based UL transmission" above may be read as "when the UE reports capability information to support non-code book-based 3TX UL transmission."

[0179] Figures 14A to 14C show an example of the correspondence between PTRS and DMRS in the non-code book-based 3TX UL transmission of this disclosure.

[0180] In STRP, if one PTRS port is configured, the instruction indicating the relationship between PTRS and DMRS (PTRS-DMRS related field) may consist of two bits as follows. This instruction may be included in DCI format 0_1 / 0_2, or it may be an instruction for each cell in DCI format 0_3.

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

[0182] Furthermore, if two PTRS ports are configured in STRP, the instruction indicating the relationship between PTRS and DMRS (PTRS-DMRS related field) may consist of one bit, as follows. This instruction may be included in DCI format 0_1 / 0_2, or it may be an instruction for each cell in DCI format 0_3.

[0183] For example, as shown in Figure 14B, an MSB value of 0 may indicate a first DMRS port sharing a PTRS port, and an MSB value of 1 may indicate a second DMRS port sharing a PTRS port.

[0184] Furthermore, in MTRP, if two PTRS ports are configured and the maximum number of ranks is 2 or 3, the instruction indicating the relationship between PTRS and DMRS (PTRS-DMRS related field) may consist of 1 bit, as follows. This instruction may be included in DCI format 0_1 / 0_2, or it may be an instruction for each cell in DCI format 0_3.

[0185] For example, as shown in Figure 14C, an MSB value of 0 may indicate a first DMRS port sharing a PTRS port, and an MSB value of 1 may indicate a second DMRS port sharing a PTRS port.

[0186] In other words, when two PTRS ports are configured, the same correspondence may apply to STRP and MTRP (when the maximum number of ranks is 2 or 3) (the correspondence in Figure 14B and Figure 14C may be the same).

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

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

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

[0190] The phrase "when 3TX UL transmission is enabled by a new RRC parameter in codebook-based UL transmission" may be read as "when the UE reports capability information to support codebook-based 3TX UL transmission."

[0191] Figures 15A to 15C show an example of the correspondence between PTRS and DMRS in the codebook-based 3TX UL transmission of this disclosure.

[0192] In STRP, if one PTRS port is configured, the instruction indicating the relationship between PTRS and DMRS (PTRS-DMRS related field) may consist of two bits as follows. This instruction may be included in DCI format 0_1 / 0_2, or it may be an instruction for each cell in DCI format 0_3.

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

[0194] Furthermore, if two PTRS ports are configured in STRP, the instruction indicating the relationship between PTRS and DMRS (PTRS-DMRS related field) may consist of one bit, as follows. This instruction may be included in DCI format 0_1 / 0_2, or it may be an instruction for each cell in DCI format 0_3.

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

[0196] Furthermore, in MTRP, if two PTRS ports are configured and the maximum number of ranks is 2 or 3, the instruction indicating the relationship between PTRS and DMRS (PTRS-DMRS related field) may consist of 1 bit, as follows. This instruction may be included in DCI format 0_1 / 0_2, or it may be an instruction for each cell in DCI format 0_3.

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

[0198] In other words, when two PTRS ports are configured, the same correspondence may apply to STRP and MTRP (when the maximum number of ranks is 2 or 3) (the correspondence in Figure 15B and Figure 15C may be the same).

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

[0200] <<Examples of Specification Descriptions>> The following are examples of specification descriptions in this disclosure. Figures 16A to 16C show an example of the correspondence between PTRS and DMRS in 3TX UL transmission in this disclosure.

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

[0202] (DCI Format 0_1) The number of bits for PTRS-DMRS related fields is determined as follows:

[0203] The value is 0 bits if any of the following conditions apply: - The PTRS setting (PTRS-UplinkConfig) is not set for either of the specific mapping types (dmrs-UplinkForPUSCH-MappingTypeA, dmrs-UplinkForPUSCH-MappingTypeB) and the transform precoder is disabled. - The transform precoder is enabled. - The maximum rank (maxRank) is 1 and the parameter related to the multipanel scheme (multipanelScheme) is not set. - The maximum rank (maxRankSfn) is 1 and the maximum rank (maxRankSfn) for SFN is 1. - The maximum number of ports for SDM (maxNrofPortsforSdm) is 1, and two PTRS ports are set, and the maximum rank (maxRankSdm) for SDM is 1.

[0204] Otherwise, it is one of 1, 2, or 4 bits, as shown below. The table / correspondence specified in the specification (see, for example, Figures 16A to 16C) is used to show the correspondence between PTRS and DMRS. DMRS ports are indicated by the antenna port field.

[0205] (If 3TX UL transmission is not enabled in STRP) If one PTRS port / two PTRS ports are set by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the SRS resource set indicator field does not exist, or the SRS resource set indicator field exists and its value is equal to "00" or "01", and the maximum number of ranks = 4, and no new RRC parameter is set to enable codebook-based 3TX UL, and no new RRC parameter is set to enable non-codebook-based 3TX UL, then it is 2 bits.

[0206] This field indicates the relationship between PTRS ports and DMRS ports corresponding to the SRS resource indicator field / precoding information and layer count field, according to a specific table / correspondence.

[0207] (If one PTRS port is configured in STRP and 3TX UL transmission is enabled) If one PTRS port is configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the SRS resource set indicator field does not exist, or the SRS resource set indicator field exists and its value is equal to "00" or "01", and the maximum rank number is 4, and a new RRC parameter is set to enable codebook-based 3TX UL, or a new RRC parameter is set to enable non-codebook-based 3TX UL, then it is 2 bits.

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

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

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

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

[0212] This field indicates the relationship between PTRS ports and DMRS ports corresponding to the SRS resource indicator field / precoding information and layer count field, according to a specific table / correspondence.

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

[0214] This field indicates the relationship between PTRS ports and DMRS ports corresponding to the SRS resource indicator field / precoding information and layer count field, according to a specific table / correspondence.

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

[0216] The MSB of the field indicates the relationship between PTRS ports and DMRS ports corresponding to the SRS resource indicator field / precoding information and layer count field, according to a specific table / correspondence.

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

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

[0219] The MSB of the field indicates the relationship between PTRS ports and DMRS ports corresponding to the SRS resource indicator field / precoding information and layer count field, according to a specific table / correspondence.

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

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

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

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

[0224] The result is 2 bits if the PTRS-DMRS related fields and the SRS resource set indicator field exist, the maximum rank number is > 2, the multipanelScheme parameter is not set, no new RRC parameter to enable codebook-based 3TX UL is set, and no new RRC parameter to enable non-codebook-based 3TX UL is set.

[0225] The value is 2 bits if the PTRS-DMRS related fields and the SRS resource set indicator field exist, the maximum rank number is > 2, the multipanelScheme parameter is not set, a new RRC parameter to enable codebook-based 3TX UL is set, or a new RRC parameter to enable non-codebook-based 3TX UL is set, and one PTRS port is set by the maxNrofPorts parameter related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig).

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

[0227] If none of the above conditions apply, the bit value is 0.

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

[0229] (DCI Format 0_2) The number of bits for PTRS-DMRS related fields is determined as follows:

[0230] The value is 0 bits if any of the following conditions apply: - The PTRS setting (PTRS-UplinkConfig) is not set for either of the specific mapping types (dmrs-UplinkForPUSCH-MappingTypeA, dmrs-UplinkForPUSCH-MappingTypeB) and the transform precoder is disabled. - The transform precoder is enabled. - The maximum rank (maxRankDCI-0-2) is 1 and the multipanel scheme parameter (multipanelScheme) is not set. - The maximum rank (maxRankDCI-0-2) is 1 and the maximum rank for SFN (maxRankSfnDCI-0-2) is 1. - The maximum rank (maxRankDCI-0-2) is 1 and the maximum rank for SDM (maxRankSdmDCI-0-2) is 1 when two PTRS ports are set by the maximum number of ports for SDM (maxNrofPortsforSdm).

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

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

[0233] This field indicates the relationship between PTRS ports and DMRS ports corresponding to the SRS resource indicator field / precoding information and layer count field, according to a specific table / correspondence.

[0234] ((When one PTRS port is configured in STRP and 3TX UL transmission is enabled)) If one PTRS port is configured by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig), the SRS resource set indicator field does not exist, or the SRS resource set indicator field exists and its value is equal to "00" or "01", and the maximum rank (maxRankDCI-0-2) = 4, and a new RRC parameter is set to enable codebook-based 3TX UL, or a new RRC parameter is set to enable non-codebook-based 3TX UL, then it is 2 bits.

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

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

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

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

[0239] This field indicates the relationship between PTRS ports and DMRS ports corresponding to the SRS resource indicator field / precoding information and layer count field, according to a specific table / correspondence.

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

[0241] This field indicates the relationship between PTRS ports and DMRS ports corresponding to the SRS resource indicator field / precoding information and layer count field, according to a specific table / correspondence.

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

[0243] The MSB of the field indicates the relationship between PTRS ports and DMRS ports corresponding to the SRS resource indicator field / precoding information and layer count field, according to a specific table / correspondence.

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

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

[0246] The MSB of the field indicates the relationship between PTRS ports and DMRS ports corresponding to the SRS resource indicator field / precoding information and layer count field, according to a specific table / correspondence.

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

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

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

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

[0251] The result is 2 bits if the PTRS-DMRS related fields and SRS resource set indicator fields exist, the maximum rank (maxRankDCI-0-2) > 2, the multipanelScheme parameter is not set, no new RRC parameter to enable codebook-based 3TX UL is set, and no new RRC parameter to enable non-codebook-based 3TX UL is set.

[0252] The value is 2 bits if the PTRS-DMRS related fields and the SRS resource set indicator field exist, and the maximum rank (maxRankDCI-0-2) > 2, the multipanel scheme parameter (multipanelScheme) is not set, a new RRC parameter to enable codebook-based 3TX UL is set, or a new RRC parameter to enable non-codebook-based 3TX UL is set, and one PTRS port is set by the parameter (maxNrofPorts) related to the maximum number of ports in the PTRS configuration (PTRS-UplinkConfig).

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

[0254] If none of the above conditions apply, the bit value is 0.

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

[0256] (DCI Format 0_3) The number of bits for PTRS-DMRS related fields is determined as follows:

[0257] The block numbers are Block Number 1, Block Number 2, ..., Block Number N ＵＬ ｃｅｌｌ It may be expressed as follows.

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

[0259] The value is 0 bits if any of the following conditions are met: • The PTRS setting (PTRS-UplinkConfig) is not configured for either of the specific mapping types (dmrs-UplinkForPUSCH-MappingTypeA, dmrs-UplinkForPUSCH-MappingTypeB), and the transform precoder is disabled, or the transform precoder is enabled, or the maximum rank (maxRankDCI) is 1.

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

[0261] The value is 2 bits if the parameter related to the maximum number of ports (maxNrofPorts) in the PTRS configuration (PTRS-UplinkConfig) is set to 1 PTRS port / 2 PTRS ports, and no new RRC parameter is set to enable codebook-based 3TX UL, and no new RRC parameter is set to enable non-codebook-based 3TX UL.

[0262] This field indicates the relationship between PTRS ports and DMRS ports corresponding to the SRS resource indicator field / precoding information and layer count field, according to a specific table / correspondence.

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

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

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

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

[0267] This embodiment clarifies the method for instructing the correspondence between PTRS and DMRS for 3TX UL transmission. Based on this instruction, the UE can appropriately control the 3TX UL transmission.

[0268] <Other> In this disclosure, setting / not setting new RRC parameters to enable codebook-based / non-codebook-based 3TX UL transmissions may be interpreted as UE reporting / not reporting capability information to support codebook-based / non-codebook-based 3TX UL transmissions.

[0269] <Supplement> <<Notification of Information to UE>> In the embodiments described above, notification of any information from the Network (NW) (e.g., Base Station (BS)) to the UE (in other words, reception of any information from the BS at the UE) may 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 signal), or a combination thereof.

[0270] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new Logical Channel ID (LCID) not defined in existing standards in the MAC subheader.

[0271] If the above notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble the Cyclic Redundancy Check (CRC) bits assigned to the DCI, or the format of the DCI.

[0272] Furthermore, the notification of arbitrary information to the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

[0273] <<Notification of Information from UE>> Notification of any information from the UE to the NW in the embodiments described above (in other words, transmission / reporting of any information from the UE to the BS) may 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.

[0274] If the above notification is made by a MAC CE, the MAC CE may be identified by including a new LCID, not specified in existing standards, in the MAC subheader.

[0275] If the above notice is made by the UCI, the notice may be transmitted using PUCCH or PUSCH.

[0276] Furthermore, the notification of any information from the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

[0277] <<Regarding the application of each embodiment>> In UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the embodiments described above may be applied (or used) if any or more of the following conditions are met: - A higher-layer parameter indicating the specific process / operation / control / assumption / information is set; - The specific process / operation / control / assumption / information is determined based on the relevant higher-layer parameter; - The specific process / operation / control / assumption / information is designated / activated / triggered by MAC CE / DCI / UCI / Resource / Channel / RS; - A specific UE capability indicating (or related to) the specific process / operation / control / assumption / information is reported or supported; - The application of the specific process / operation / control / assumption / information is determined based on specific conditions.

[0278] The specific UE capability may represent at least one of the following: supporting specific processing / operation / control / information for at least one of the embodiments described above; supporting 3TX UL transmission; supporting multiple different antenna layouts / number of antenna groups; supporting coherent groups; supporting coherent types (fully coherent / partially coherent / non-coherent); and supporting a number of candidate precoders.

[0279] Furthermore, the above-mentioned specific UE capability may be a capability that applies across all frequencies (commonly regardless of frequency), a capability per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), a capability per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), a capability per subcarrier spacing (SCS), or a capability per feature set (FS) or feature set per component-carrier (FSPC).

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

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

[0282] (Note) The following inventions are added with respect to one embodiment of the present disclosure. [Note 1] A terminal having a receiving unit that receives upper layer parameters for a non-code book-based uplink (UL) transmission utilizing three antenna ports (3TX), and a control unit that controls the activation of the non-code book-based 3TX UL transmission based on the upper layer parameters. [Note 2] The terminal according to Note 1, wherein the receiving unit receives the upper layer parameters for each measurement reference signal (SRS) resource set or for each cell. [Note 3] The terminal according to Note 1 or Note 2, wherein, when the non-code book-based 3TX UL transmission is activated, the receiving unit receives downlink control information (DCI) including a field indicating the correspondence between phase tracking reference signals (PTRS) and demodulation reference signals (DMRS). [Note 4] When the non-code book-based 3TX UL transmission is enabled, the receiving unit receives downlink control information (DCI) including a field indicating the correspondence between the phase tracking reference signal (PTRS) and the demodulation reference signal (DMRS), the number of bits in the field differs depending on the number of PTRS ports set, and the terminal is one of those described in Notes 1 to 3.

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

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

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

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

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

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

[0289] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC).

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

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

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

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

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

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

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

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

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

[0299] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20.

[0300] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.

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

[0302] Furthermore, the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. Furthermore, PDSCH may be read as DL data, and PUSCH may be read as UL data.

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

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

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

[0306] In this disclosure, downlinks, uplinks, etc., may be expressed without the word "link." Also, the word "physical" may be omitted from the beginning of each channel.

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

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

[0309] Furthermore, in the wireless communication system 1, the uplink reference signal (UL-RS) may include a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. The DMRS may also be called a user-specific reference signal (UE-specific Reference Signal).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0327] The transmitting / receiving unit 120 may transmit upper layer parameters for non-codebook-based uplink (UL) transmission using three antenna ports (3TX). The control unit 110 may perform control to receive the non-codebook-based 3TX UL transmission activated based on the upper layer parameters from the terminal.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0344] The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources may be, for example, Non Zero Power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources may be at least one of the following: NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. CSI-IM may also be called CSI-Interference Management (IM), and may be interpreted interchangeably with Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., may be interpreted interchangeably.

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

[0346] The transmitting / receiving unit 220 may perform at least one of the above-described transmitting / receiving unit processes.

[0347] The control unit 210 may perform at least one of the control unit processes described above.

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

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

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

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

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

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

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

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

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

[0357] The storage 1003 is a computer-readable recording medium and may consist of at least one of the following: a flexible disk, a floppy disk, a magneto-optical disk (e.g., a Compact Disk (Compact Disc ROM (CD-ROM)), a Digital Use Disk, a Blu-ray (registered trademark) disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. The storage 1003 may also be called an auxiliary storage device.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0372] A TTI with a time length of 1 ms may be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0394] In this disclosure, terms such as “precoding,” “precoder,” “weight (precoding weight),” “quasi-co-location (QCL),” “transmission configuration indication state (TCI state),” “spatial relation,” “spatial domain filter,” “transmit power,” “phase rotation,” “antenna port,” “layer,” “number of layers,” “rank,” “resource,” “resource set,” “beam,” “beam width,” “beam angle,” “antenna,” “antenna element,” “panel,” “UE panel,” “transmitting entity,” and “receiving entity” may be used interchangeably.

[0395] In this disclosure, "antenna port" may be interpreted interchangeably with "antenna port for any signal / channel" (e.g., a Demodulation Reference Signal (DMRS) port). In this disclosure, "resource" may be interpreted interchangeably with "resource for any signal / channel" (e.g., a reference signal resource, an SRS resource, etc.). Resources may include time / frequency / code / spatial / power resources. Furthermore, a spatial domain transmit filter may include at least one of a spatial domain transmit filter and a spatial domain receive filter.

[0396] The above group may include, for example, at least one of the following: a spatial relationship group, a code division multiplexing (CDM) group, a reference signal (RS) group, a control resource set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, or a panel group.

[0397] Furthermore, in this disclosure, terms such as beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), and RS may be interpreted interchangeably.

[0398] Furthermore, in this disclosure, TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc., may be interpreted interchangeably.

[0399] Furthermore, in this disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interpreted interchangeably.

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

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

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

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

[0404] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform a control / operation based on said information.

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

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

[0407] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a moving object, the moving object itself, etc.

[0408] The term "mobile object" refers to any movable object, regardless of its speed, and naturally includes cases where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items carried on them. Furthermore, such mobile objects may be autonomously driven objects operating based on operational commands.

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

[0410] Figure 21 shows 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 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 rotation speed sensor 51, a pneumatic pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

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

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

[0413] Signals from various sensors 50-58 include current signals from current sensor 50 for sensing motor current, rotational speed signals of front wheels 46 / rear wheels 47 acquired by rotational speed sensor 51, air pressure signals of front wheels 46 / rear wheels 47 acquired by air pressure sensor 52, vehicle speed signals acquired by vehicle speed sensor 53, acceleration signals acquired by acceleration sensor 54, accelerator pedal depression amount signals acquired by accelerator pedal sensor 55, brake pedal depression amount signals acquired by brake pedal sensor 56, operation signals of shift lever 45 acquired by shift lever sensor 57, and detection signals acquired by object detection sensor 58 for detecting obstacles, vehicles, pedestrians, etc.

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

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

[0416] The driver assistance system unit 64 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driver assistance functions or autonomous driving functions.

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

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

[0419] The communication module 60 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 50-58 input to the electronic control unit 49, information obtained based on said 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., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include the information based on the above input.

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

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

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

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

[0424] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes having base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), etc., but not limited to these), or a combination thereof.

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

[0426] Each aspect / embodiment described in this disclosure is 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 (where x is, for example, an integer or decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, systems utilizing Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, and next-generation systems extended, modified, created, or defined based thereon may also be applied. Furthermore, multiple systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).

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

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

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

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

[0431] Furthermore, “judgment (decision)” may be considered as “judgment (decision)” of resolving, selecting, choosing, establishing, comparing, etc. In other words, “judgment (decision)” may be considered as “judgment (decision)” of some action. In this disclosure, “judgment (decision)” may be interpreted as mutually interchangeable with the actions described above.

[0432] Furthermore, in this disclosure, “determine / determining” may be interpreted as “assume / assuming,” “expect / expecting,” or “consider / considering.” In addition, in this disclosure, “not expecting to do…” may be interpreted as “expecting not to do….”

[0433] In this disclosure, "expect" may be interpreted as "be expected." For example, "expect(s) ..." (where "..." may be expressed as, for example, a that clause or an infinitive) may be interpreted as "be expected ...." Similarly, "does not expect ..." may be interpreted as "be not expected ...." Furthermore, "An apparatus A is not expected ..." may be interpreted as "An apparatus B other than apparatus A does not expect ..." (for example, if apparatus A is a UE, apparatus B may be a base station).

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

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

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

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

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

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

[0440] In this disclosure, terms such as "less than or equal to," "less than," "greater than or equal to," "more than," and "equal to" may be interpreted interchangeably. In addition, in this disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees. Furthermore, in this disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees, by adding "i-th" (where i is any integer) to the expression (for example, "highest" may be interpreted interchangeably as "i-th highest").

[0441] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.

[0442] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "B based on A", "B during / while A", "B before A", "B at (the same time as) / on A", "B after A", "B since A", and "B until A" may be interchangeable. Furthermore, A, B, etc., may be replaced with appropriate expressions such as nouns, gerunds, or regular sentences depending on the context. The time difference between A and B may be approximately zero (immediately after or immediately before). Additionally, a time offset may be applied to the time when A occurs. For example, "A" may be interpreted as "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predetermined or determined by the UE based on notified information.

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

[0444] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The descriptions herein are illustrative and not intended to be restrictive in any way to the invention described herein.

[0445] This application is based on Japanese Patent Application No. 2025-024524, filed on February 18, 2025. All of its contents are included herein.

Claims

1. A terminal having a receiving unit that receives upper layer parameters for non-code book-based (3TX) uplink (UL) transmission using three antenna ports, and a control unit that controls the activation of non-code book-based 3TX UL transmission based on the upper layer parameters.

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

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

4. When the non-codebook-based 3TX UL transmission is enabled, the receiving unit receives downlink control information (DCI) including a field indicating the correspondence between phase tracking reference signals (PTRS) and demodulation reference signals (DMRS), wherein the number of bits in the field differs depending on the number of PTRS ports set, as described in claim 1.

5. A wireless communication method for a terminal, comprising the steps of: receiving upper layer parameters for a non-code book-based uplink (UL) transmission utilizing three antenna ports (3TX); and controlling the activation of the non-code book-based 3TX UL transmission based on the upper layer parameters.

6. A base station having a transmitting unit that transmits upper layer parameters for a non-code book-based (3TX) uplink (UL) transmission using three antenna ports, and a control unit that performs control to receive a non-code book-based 3TX UL transmission activated based on the upper layer parameters from a terminal.

Images