Terminal, wireless communication method, base station, and system

Abstract

A terminal according to one aspect of the present disclosure includes: a reception unit that receives downlink control information including a field indicating an association between an uplink phase tracking reference signal (PTRS) and an uplink shared channel (PUSCH) demodulation reference signal (DMRS); and a control unit that determines the PTRS-DMRS association on the basis of the field. If the number of PUSCH ranks or the number of layers is greater than a prescribed number, the size of the field changes, or the PTRS-DMRS association is specified according to the combination of the field and another piece of information.

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

[0003] Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later, 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] In existing wireless communication systems (e.g., Rel. 16), up to four layers or antenna ports (e.g., DMRS antenna ports / PUSCH antenna ports) are supported in UL transmission (e.g., uplink shared channel (PUSCH)). Furthermore, assuming up to four layers or antenna ports, a correspondence / association between an antenna port for a first signal and an antenna port for a second signal is specified. The first signal may be, for example, an uplink phase tracking reference signal (PTRS), and the second signal may be, for example, a demodulation reference signal for PUSCH (e.g., a demodulation reference signal (DMRS)).

[0006] On the other hand, it is expected that future wireless communication systems (for example, Rel. 18 and later / Beyond 5G and later / 6G and later) will support more than four layers or antenna ports.

[0007] However, in such a case, how to control the correspondence relationship between the antenna port of the first signal and the antenna port of the second signal becomes an issue. If the correspondence relationship between the antenna port of the first signal and the antenna port of the second signal is not appropriately controlled, there is a risk of a decrease in throughput or a deterioration in communication quality.

[0008] Therefore, one of the objectives of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately perform UL transmission even when the number of layers or the number of antenna ports used for UL transmission is expanded.

[0009] A terminal according to one aspect of the present disclosure includes a receiving unit that receives downlink control information including a field that indicates an association between a uplink phase tracking reference signal (PTRS) and a demodulation reference signal (DMRS) for an uplink shared channel (PUSCH), and a control unit that determines the association between the PTRS and the DMRS based on the field, and when the rank number or layer number of the PUSCH is larger than a predetermined number, the size of the field is changed, or the association between the PTRS and the DMRS is indicated by a combination of the field and other information.

[0010] According to one aspect of the present disclosure, UL transmission can be performed appropriately even when the number of layers or the number of antenna ports used for UL transmission is expanded.

[0011] Figure 1 shows an example of the association between precoder types and TPMI indexes. Figures 2A and 2B show an example of single-panel UL transmission. Figures 3A to 3C show examples of methods 1 to 3 for simultaneous UL transmission using multiple panels. Figures 4A to 4C show an example of a PUSCH transmission method. Figures 5A to 5C show another example of a PUSCH transmission method. Figures 6A and 6B show an example of a PTRS-DMRS association field in Rel. 16. Figure 7 shows an example of DMRS port-PUSCH antenna port-PTRS port association (or association candidates). Figure 8 shows an example of a PTRS-DMRS association field in Rel. 17. Figures 9A and 9B show another example of a PTRS-DMRS association field in Rel. 17. 10A and 10B are diagrams illustrating an example of the bit size of a predetermined field (e.g., a PTRS-DMRS association field) of DCI according to the first embodiment. FIG. 11 is a diagram illustrating an example of association between a PTRS and a DMRS indicated by a predetermined field (e.g., a PTRS-DMRS association field) of DCI according to the first embodiment. FIG. 12 is a diagram illustrating an example of the size of a predetermined field (e.g., a PTRS-DMRS association field) of DCI according to the second embodiment. FIG. 13A and 13B are diagrams illustrating an example of association between a PTRS and a DMRS indicated by a predetermined field (e.g., a PTRS-DMRS association field) of DCI according to the third embodiment. FIG. 14 is a diagram illustrating an example of association (or association candidates) between a DMRS port, a PUSCH antenna port, and a PTRS port according to the third embodiment. Fig. 15 is a diagram showing an example of association between PTRS and DMRS indicated by a predetermined field (for example, a PTRS-DMRS association field) of DCI according to the third embodiment. Fig. 16 is a diagram showing another example of association (or association candidates) between DMRS port, PUSCH antenna port, and PTRS port according to the third embodiment. Fig. 17 is a diagram showing another example of association between PTRS and DMRS indicated by a predetermined field (for example, a PTRS-DMRS association field) of DCI according to the third embodiment.FIG. 18 is a diagram illustrating another example of association (or association candidates) between DMRS ports, PUSCH antenna ports, and PTRS ports according to the third embodiment. FIG. 19 is a diagram illustrating another example of association between PTRS and DMRS indicated by a predetermined field (e.g., a PTRS-DMRS association field) of DCI according to the third embodiment. FIGS. 20A and 20B are diagrams illustrating an example of a predetermined field (e.g., a PTRS-DMRS association field) of DCI according to the present embodiment. FIG. 21 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 22 is a diagram illustrating an example of a configuration of a base station according to an embodiment. FIG. 23 is a diagram illustrating an example of a configuration of a user terminal according to an embodiment. FIG. 24 is a diagram illustrating an example of hardware configurations of a base station and a user terminal according to an embodiment. FIG. 25 is a diagram illustrating an example of a vehicle according to an embodiment.

[0012] (PUSCH Precoder) In NR, it is being considered that a UE will support at least one of codebook (CB)-based transmission and non-codebook (NCB)-based transmission.

[0013] For example, it is being considered that the UE determines a precoder (precoding matrix) for CB-based and / or NCB-based Physical Uplink Shared Channel (PUSCH) transmission using at least a Sounding Reference Signal (SRS) resource indicator (SRI).

[0014] In the case of CB-based transmission, the UE may determine a precoder for PUSCH transmission based on the SRI, a Transmitted Rank Indicator (TRI), a Transmitted Precoding Matrix Indicator (TPMI), etc. In the case of NCB-based transmission, the UE may determine a precoder for PUSCH transmission based on the SRI.

[0015] The 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 may be specified by the parameter "srs-ResourceIndicator" included in the RRC information element "ConfiguredGrantConfig" of the configured grant PUSCH. The TRI and TPMI may be specified by the "Precoding information and number of layers" field of the DCI.

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

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

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

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

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

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

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

[0023] The precoder type may be interpreted as coherency, PUSCH transmission coherence, coherent type, coherence type, codebook type, codebook subset, codebook subset type, or the like.

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

[0025] Fig. 1 is a diagram showing an example of association between precoder types and TPMI indexes. Fig. 1 corresponds to a table of precoding matrices W for single-layer (rank 1) transmission using four antenna ports in DFT-s-OFDM (Discrete Fourier Transform spread OFDM, transform precoding is effective).

[0026] In Fig. 1, when the precoder type (codebookSubset) is fully, partial, and noncoherent (fullyAndPartialAndNonCoherent), the UE is notified of a TPMI of any one of 0 to 27 for single layer transmission. Also, when the precoder type is partial and noncoherent (partialAndNonCoherent), the UE is configured with a TPMI of any one of 0 to 11 for single layer transmission. When the precoder type is noncoherent, the UE is configured with a TPMI of any one of 0 to 3 for single layer transmission.

[0027] As shown in Fig. 1, a precoding matrix in which only one element in each column is non-zero may be called a non-coherent codebook. A precoding matrix in which a predetermined number (not all) of elements in each column are non-zero 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.

[0028] Non-coherent and partially coherent codebooks may be referred to as antenna selection precoders, and fully coherent codebooks may be referred to as non-antenna selection precoders.

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

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

[0031] (Spatial Relationship for SRS, PUSCH) The UE may receive information (SRS configuration information, e.g., parameters in the RRC control element "SRS-Config") used for transmitting measurement reference signals (e.g., Sounding Reference Signals (SRS)).

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

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

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

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

[0036] Furthermore, the usage ("usage" of the RRC parameter, "SRS-SetUse" of the L1 (Layer-1) parameter) may be, for example, beam management, codebook-based transmission (codebook: CB), non-codebook-based transmission (non-Codebook: NCB), antenna switching, etc. The SRS for the codebook-based transmission or non-codebook-based transmission may be used to determine a precoder for codebook-based or non-codebook-based PUSCH transmission based on the SRI.

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

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

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

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

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

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

[0043] In NR, the transmission of uplink signals may be controlled based on the presence or absence of beam correspondence (BC). BC may be, for example, the ability of a node (e.g., a base station or a UE) to determine the beam to be used for transmitting a signal (transmit beam, Tx beam) based on the beam to be used for receiving the signal (receive beam, Rx beam).

[0044] BC may also be referred to as transmit / receive beam correspondence (Tx / Rx beam correspondence), beam reciprocity, beam calibration, calibrated / non-calibrated, reciprocity calibrated / non-calibrated, correspondence, agreement, etc.

[0045] For example, in the absence of BC, the UE may transmit an uplink signal (e.g., PUSCH, PUCCH, SRS, etc.) using the same beam (spatial domain transmit filter) as the SRS (or SRS resource) instructed by the base station based on the measurement results of one or more SRSs (or SRS resources).

[0046] On the other hand, when BC is present, the UE may transmit an uplink signal (e.g., a PUSCH, a PUCCH, an SRS, etc.) using a beam (spatial domain transmit filter) that is the same as or corresponds to the beam (spatial domain receive filter) used to receive a specified SSB or CSI-RS (or CSI-RS resource).

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

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

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

[0050] When codebook-based transmission is used for PUSCH, two SRS resources may be configured for the UE by RRC, and one of the two SRS resources may be indicated by a DCI (a 1-bit predetermined field). When non-codebook-based transmission is used for PUSCH, four SRS resources may be configured for the UE by RRC, and one of the four SRS resources may be indicated by a DCI (a 2-bit predetermined field). To use a spatial relationship other than the two or four spatial relationships configured by RRC, an RRC reconfiguration is required.

[0051] In addition, the DL-RS can be configured for the spatial relationship of the SRS resources used for the PUSCH. For example, for SP-SRS, the UE can be configured by RRC with the spatial relationship of multiple (e.g., up to 16) SRS resources, and one of the multiple SRS resources can be indicated by MAC CE.

[0052] Incidentally, future wireless communication systems (e.g., Rel. 18 NR and later) are expected to support simultaneous UL transmission (e.g., simultaneous multi-panel UL transmission (SiMPUL)) using multiple beams / panels / TRPs toward one or more transmission / reception points (TRPs).

[0053] For example, Rel. 18 considers simultaneous UL transmission using up to two TRPs per two panels. It also considers single-DCI-based and multi-DCI-based multi-TRP operation, and assumes that the total number of layers across all panels is up to four, and the total number of codewords across all panels is up to two. Of course, the number of TRPs, panels, layers, and codewords are not limited to these.

[0054] (Single Panel Transmission) The single panel UL transmission scheme or a candidate single panel UL transmission scheme may employ at least one of the following transmission schemes A and B (single panel UL transmission schemes A and B). In the present disclosure, a panel / UE panel may be interpreted as a UE capability value set (e.g., a UE capability value set) reported for each UE capability. In the present disclosure, different panels, different spatial relationships, different joint TCI states, different TPC parameters, different antenna ports, etc. may be interpreted as interchangeable terms.

[0055] Transmission Scheme A: Single Panel Single TRP UL Transmission In Rel. 15 and Rel. 16, a transmission scheme is used in which a UE transmits UL for one TRP at a time from only one beam and panel (FIG. 2A).

[0056] [Transmission Scheme B: Single Panel Multi-TRP UL Transmission] Rel. 17 considers UL transmission from only one beam and panel at a time and repeated transmission for multiple TRPs (Fig. 2B). In the example of Fig. 2B, the UE transmits a PUSCH from panel #1 to TRP #1 (switching beams and panels), and then transmits a PUSCH from panel #2 to TRP #2. The two TRPs are connected via an ideal backhaul.

[0057] (Multi-Panel Transmission) In Rel. 18 and later, in order to improve UL throughput / reliability, support for simultaneous UL transmission using multiple panels (e.g., simultaneous multi-panel UL transmission (SiMPUL)) or simultaneous transmission across multiple panels (STxMP)) for one or more TRPs is being considered. Also, a multi-panel UL transmission scheme is being considered for a specific UL channel (e.g., PUSCH / PUCCH).

[0058] For example, up to X (e.g., X = 2) and up to Y (e.g., Y = 2) panels may be supported for multi-panel UL transmission. In multi-panel UL transmission, if UL precoding indication for PUSCH is supported, a codebook of a legacy system (e.g., pre-Rel. 16) may be supported for simultaneous multi-panel transmission. Considering single DCI and multi-DCI-based multi-TRP operation, the number of layers may be up to x (e.g., x = 4) across all panels, and the number of codewords (CWs) may be up to y (e.g., y = 2) across all panels.

[0059] At least one of the following methods 1 to 3 (multi-panel UL transmission methods 1 to 3) is being considered as a multi-panel UL transmission method or a candidate multi-panel UL transmission method. Only one of transmission methods 1 to 3 may be supported. Multiple methods including at least one of transmission methods 1 to 3 may be supported, and one of the multiple transmission methods may be configured in the UE.

[0060] <Transmission Scheme 1: Coherent Multi-Panel UL Transmission> Multiple panels may be synchronized with each other. All layers are mapped to all panels. Multiple analog beams are directed. The SRS Resource Indicator (SRI) field may be extended. This scheme may use up to 4 layers for UL.

[0061] In the example of Figure 3A, the UE maps one codeword (CW) or one transport block (TB) to L layers (PUSCH (1, 2, ..., L)) and transmits the L layers from each of two panels. Panels #1 and #2 are coherent. Transmission scheme 1 can obtain diversity gain. The total number of layers in the two panels is 2L. If the maximum total number of layers is 4, the maximum number of layers in one panel is 2.

[0062] <Transmission Scheme 2: Non-coherent Multi-Panel UL Transmission of One Codeword (CW) or Transport Block (TB)> The multiple panels may not be synchronized. Different layers are mapped to one CW or TB for different panels and PUSCHs from multiple panels. A layer corresponding to one CW or TB may be mapped to multiple panels. This transmission scheme may use up to four layers or up to eight layers for the UL. If up to eight layers are supported, this transmission scheme may support one CW or TB using up to eight layers.

[0063] In the example of FIG. 3B, the UE maps 1 CW or 1 TB to k layers (PUSCH(1, 2, ..., k)) and L-k layers (PUSCH(k+1, k+2, ..., L)), transmits k layers from panel #1, and transmits L-k layers from panel #2. Transmission scheme 2 can obtain gains through multiplexing and diversity. The total number of layers in the two panels is L.

[0064] <Transmission Scheme 3: Non-coherent Multi-Panel UL Transmission of Two CWs or TBs> The multiple panels may not be synchronized. Different layers are mapped to different panels and two CWs or TBs for PUSCHs from the multiple panels. A layer corresponding to one CW or TB may be mapped to one panel. Layers corresponding to multiple CWs or TBs may be mapped to different panels. This transmission scheme may use up to four layers or up to eight layers for the UL. When up to eight layers are supported, this transmission scheme may support up to four layers per CW or TB.

[0065] In the example of FIG. 3C , the UE maps CW#1 or TB#1 of the 2CWs or 2TBs to k layers (PUSCH (1, 2, ..., k)), maps CW#2 or TB#2 to L-k layers (PUSCH (k+1, k+2, ..., L)), and transmits k layers from panel #1 and L-k layers from panel #2. Transmission scheme 3 can obtain gains through multiplexing and diversity. The total number of layers in the two panels is L.

[0066] In each of the above transmission schemes, the base station may configure or indicate panel-specific transmission for UL transmission using UL TCI or panel ID. UL TCI (UL TCI state) may be based on signaling similar to DL beam indication supported in Rel. 15. The panel ID may be implicitly or explicitly applied to transmission of at least one of the target RS resource or target RS resource set, PUCCH, SRS, and PRACH. When the panel ID is explicitly signaled, the panel ID may be configured in at least one of the target RS, target channel, and reference RS (e.g., DL RS resource configuration or spatial relationship information).

[0067] In one or more of the transmission methods / modes described above, multi-panel UL transmission (e.g., Simultaneous Transmission across Multiple Panels (STxMP)) for scheduling a PUSCH based on one DCI (single DCI) / scheduling a PUSCH based on multiple DCIs (multiple DCIs) is being considered.

[0068] In simultaneous multi-panel transmission (STxMP) in a single DCI-based multi-TRP system, the following schemes may be applied to UL transmissions (e.g., PUSCH): Space Division Multiplexing (SDM): Different layers / DMRS ports of one PUSCH are separately precoded and transmitted simultaneously from different UE beams / panels (see Figures 4A and 4B); SDM repetition: Two PUSCH transmission opportunities with different redundancy versions (RVs) of the same TB are transmitted simultaneously from two different UE beams / panels on the same time and frequency resources (see Figure 4C); and Frequency Division Multiplexing (FDM)-A: Different portions of the frequency domain resources of one PUSCH transmission opportunity (e.g., one PUSCH transmission occasion) are transmitted from different UE beams / panels (see Figure 5A). FDM-B scheme: Two PUSCH transmission opportunities with the same / different RVs of the same TB are transmitted from different UE beams / panels on non-overlapping frequency and time domain resources (see Figure 5B). SFN-based transmission scheme: All the same layers / DMRS ports of one PUSCH are transmitted simultaneously from two different UE beams / panels (see Figure 5C).

[0069] In the present disclosure, the terms "repeated transmission" and "transmission" may be interchangeable. Transmitting multiple TBs may mean transmitting the same TB multiple times or transmitting different TBs.

[0070] Space Division Multiplexing (SDM) The UE may assume that repeated PUSCH transmissions employing Space Division Multiplexing (SDM) are scheduled on the same time and frequency resources, i.e., the UE may transmit repeated PUSCH transmissions employing SDM on the same time and frequency resources when using coherent panels.

[0071] 4A is a diagram showing an example of repeated transmission using SDM in one CW, in which the time and frequency resources of layers #1-2 and #3-4 corresponding to the PUSCH / PUCCH are the same.

[0072] 4B is a diagram showing an example of repeated transmission using SDM in two CWs, in which CW#1 and CW#2 corresponding to PUSCH / PUCCH have the same time and frequency resources.

[0073] 4C is a diagram showing an example of repeated transmission using SDM, in which the time and frequency resources of PUSCH / PUCCH repetition #1 and repetition #2 are the same.

[0074] Note that PUSCH transmission to which SDM is applied (for example, PUSCH repeated transmission) may be configured such that at least a portion of the time and frequency resources overlap.

[0075] Frequency Division Multiplexing (FDM) The UE may assume that PUSCH / PUCCH repeat transmissions employing Frequency Division Multiplexing (FDM) are scheduled on the same time resources but different frequency resources, i.e., the UE may transmit PUSCH / PUCCH repeat transmissions employing FDM on the same time resources but different frequency resources when using coherent panels.

[0076] 5A is a diagram showing a first example of repeated transmission using FDM (FDM-A), in which one PUSCH / PUCCH repeated transmission is performed for one TB / UCI.

[0077] 5B is a diagram showing a second example of repeated transmission using FDM (FDM-B), in which PUSCH / PUCCH repeated transmission is performed twice per TB / UCI.

[0078] 5C is a diagram illustrating an example of repeated transmission using a single frequency network (SFN), in which one PUSCH / PUCCH is transmitted using a different beam / panel for one TB / UCI.

[0079] <PTRS> Rel. 15 NR supports a Phase Tracking Reference Signal (PTRS). A base station may transmit the PTRS in the downlink. The base station may map the PTRS contiguously or discontinuously in the time direction to a predetermined number of subcarriers (e.g., one subcarrier) and transmit the PTRS.

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

[0081] The UE may also transmit the PTRS on the uplink. The UE may map the PTRS contiguously or discontinuously in the time direction on a predetermined number of subcarriers (for example, one subcarrier) and transmit the PTRS.

[0082] For example, the UE may transmit the PTRS during at least a portion of a period (slot, symbol, etc.) in which the Physical Uplink Shared Channel (PUSCH) is scheduled (in other words, the period in which the PUSCH is transmitted). The PTRS transmitted by the UE may be referred to as an UL PTRS.

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

[0084] The UE may be configured with PTRS configuration information (PTRS-DownlinkConfig for DL ​​and PTRS-UplinkConfig for UL) using higher layer signaling. For example, the PTRS configuration information may be included in configuration information (DMRS-DownlinkConfig, DMRS-UplinkConfig) of a demodulation reference signal (DMRS) for PDSCH or PUSCH.

[0085] <PTRS and DMRS> In NR (e.g., Rel. 15), a DMRS port associated with a PTRS port is assumed to be QCL with respect to QCL types A and D. In other words, when a PTRS port is associated with a DMRS port, the PTRS port and the DMRS port may be assumed to be in a QCL type A and D relationship with each other.

[0086] Rel. 16 NR supports the association between a PTRS port and a DMRS port (e.g., PTRS-DMRS association) being indicated by a predetermined field in the DCI. The predetermined field may be referred to as a PTRS-DMRS association field or a PTRS-DMRS association field (e.g., a PTRS-DMRS association field).

[0087] Meanwhile, Rel. 16 NR has agreed to support up to two PTRS ports (a first PTRS port and a second PTRS port) for single PDCCH-based multi-panel / TRP transmission. The number of applied / configured PTRS ports (e.g., one or two PTRS ports) may be signaled to the UE by a higher layer parameter.

[0088] When one PTRS port (e.g., PTRS port #0) is configured, the association between the PTRS and the DMRS may be determined based on the code points specified in the PTRS-DMRS association field of the DCI and the correspondence (e.g., table) between each code point and the DMRS port. The correspondence (e.g., table) between each code point and the DMRS port may be predefined (see FIG. 6A).

[0089] Figure 6A shows a case where each code point (here, 0 to 3) in the PTRS-DMRS related field corresponds to a specific DMRS port (here, the first to fourth scheduled DMRS ports correspond, respectively).

[0090] When two PTRS ports (e.g., PTRS port #0 and PTRS port #1) are configured, the association between each PTRS and the DMRS may be determined based on the code points specified in the PTRS-DMRS association field of the DCI and the correspondence (e.g., table) between each code point and the DMRS port. The correspondence (e.g., table) between each code point and the DMRS port may be defined in advance (see FIG. 6B).

[0091] For example, some of the code points (e.g., the most significant bit (MSB)) may be used to specify the DMRS port for PTRS port #0, and the remaining code points (e.g., the least significant bit (LSB)) may be used to specify the DMRS port for PTRS port #1.

[0092] 6B shows a case where the first DMRS among the DMRSs sharing PTRS #0 is designated when the MSB (here, 1 bit) is 0, and the second DMRS among the DMRSs sharing PTRS #0 is designated when the MSB is 1. Also, a case where the first DMRS among the DMRSs sharing PTRS #0 is designated when the LSB (here, 1 bit) is 0, and the second DMRS among the DMRSs sharing PTRS #0 is designated when the MSB is 1, is shown.

[0093] Information regarding the DMRS (e.g., first DMRS / second DMRS) that shares each PTRS (here, PTRS #0, #1) may be specified in advance, or may be explicitly or implicitly notified by the base station to the UE via DCI / RRC.

[0094] For example, a PUSCH antenna port corresponding to each PTRS port may be defined / configured in advance, and predetermined information regarding the correspondence between the PUSCH antenna port and the DMRS port may be notified to the UE by DCI / RRC. The UE may determine the association between the DMRS port and the PTRS port based on the information regarding the correspondence between the DMRS port and the PUSCH antenna port notified from the base station and the predefined correspondence between the PUSCH antenna port and the PTRS port.

[0095] The predetermined information regarding the correspondence between the PUSCH antenna ports and the DMRS ports may be indicated to the UE by a predetermined field included in the DCI (e.g., the DCI used for scheduling the PUSCH). The predetermined field may be at least one of a "Precoding information and number of layers" field and an "Antenna ports" field.

[0096] For example, it may be defined that PUSCH antenna ports 1000 and 1002 in a designated Transmitted Precoding Matrix Indicator (TPMI) share PTRS port #0, and PUSCH antenna ports 1001 and 1003 in a designated TPMI share PTRS port #1. The TPMI may be specified by the "Precoding information and number of layers" field of the DCI (see FIG. 7).

[0097] PTRS port #0 may be associated with UL layer 'x' of multiple layers transmitted on PUSCH antenna port 1000 and PUSCH antenna port 1002 in the indicated TPMI. PTRS port #1 may be associated with UL layer 'y' of multiple layers transmitted on PUSCH antenna port 1001 and PUSCH antenna port 1003 in the indicated TPMI. x / y may be provided by a PTRS-DMRS association field included in the DCI (e.g., FIG. 6B).

[0098] The specifications may define that PUSCH antenna ports 1000 and 1002 share PTRS port #0, and that PUSCH antenna ports 1001 and 1003 share PTRS port #1. Predetermined information from the base station (hereinafter also referred to simply as "TPMI") may indicate which layer / DMRS port is transmitted from which PUSCH antenna port. This means that the TPMI indicates which layer / DMRS port shares which PTRS port. The PTRS-DMRS association field may indicate that one layer / DMRS port from multiple layers / DMRS ports shares the PTRS port.

[0099] Rel. 17 supports multi-TRP PUSCH repetition using time division multiplexing (TDM) (e.g., TDM M-TRP PUSCH repetition), and PTRS-DMRS association may be indicated on a per-TRP basis.

[0100] When a maximum rank is two (e.g., maxrank=2) and one PTRS port is used, the PTRS-DMRS association of two TRPs may be indicated by a PTRS-DMRS association field (e.g., one field). For example, the MSB of the PTRS-DMRS association field may indicate the first TRP, and the LSB of the PTRS-DMRS association field may indicate the second TRP (see FIG. 8).

[0101] When one or two PTRS ports are used with a maximum rank greater than two (e.g., maxrank>2), the PTRS-DMRS association of the two TRPs may be indicated by a PTRS-DMRS association field and a second PTRS-DMRS association field (see Figures 9A and 9B). Figure 9A shows an example of the PTRS-DMRS association field when one PTRS is configured / applied, and Figure 9B shows an example of the PTRS-DMRS association field when two PTRSs are configured / applied.

[0102] Incidentally, it is expected that future wireless communication systems (e.g., Rel. 18 NR) will support more than four ranks (>4 ranks) in UL transmission (e.g., PUSCH transmission).

[0103] In existing systems (e.g., Rel. 15-17), the maximum number of PTRS ports is 2. The problem is how to set / apply the number of PTRS ports for PUSCHs with ranks greater than 4 (e.g., PUSCH > rank 4) (e.g., whether to support 2 or 4 ports).

[0104] For example, for PUSCH with ranks greater than 4, the number of antenna coherent groups (Ng) is considered to be 1, 2, or 4. The UE assumes that antenna ports within the Ng antenna coherent groups are coherent, and that other antenna ports are non-coherent. When Ng=1, full coherence may be assumed.

[0105] If different antenna groups do not share the same power amplifier (PA), it is expected that different phase noises will be observed for each antenna group. Therefore, each DMRS port is associated with one PTRS port, and it is being considered to set the maximum number of PTRS ports to a value greater than two (e.g., four). For example, it is expected that up to two or four PTRS ports will be supported for CP-OFDM for 8Tx PUSCH.

[0106] In such a case, the problem arises as to how to set / indicate / control the PTRS-DMRS association (or the correspondence between the PUSCH antenna port and the PTRS port).

[0107] Therefore, the inventors of the present invention have considered a method for appropriately controlling UL transmission even when more than a specified rank / specified layer (e.g., 4 rank / 4 layers) of PUSHs are supported, and have come up with the present embodiment.

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

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

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

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

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

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

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

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

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

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

[0118] (Wireless communication method) When a UE performs UL transmission (e.g., PUSCH transmission) using ranks / layers greater than a predetermined value (e.g., 4), the UE may determine an association between a DMRS port (or a PUSCH antenna port) associated with the UL transmission and a PTRS port based on a predetermined condition. The predetermined condition may be at least one of a transmission scheme applied / configured for UL transmission (e.g., PUSCH), a PTRS-DMRS association (e.g., a PTRS-DMRS association) field indicated by DCI, the number of PTRS ports applied / configured, a Transmitted Precoding Matrix Indicator (TPMI) field, and predetermined information (or a combination of two or more of these). The predetermined information may be information indicated / configured by DCI / higher layer parameters (e.g., information regarding UL transmission / information regarding parameters applied to UL transmission).

[0119] The PTRS-DMRS-related field / TPMI-related field may be included in the DCI scheduling the PUSCH. At least one of the number of bits and the number of fields of the PTRS-DMRS-related field / TPMI-related field included in the DCI may be defined in a specification, may be set by a higher layer parameter / DCI, or may be variable based on a predetermined parameter. The predetermined parameter may be, for example, at least one of the number of PTRS ports to be applied / set and a transmission method.

[0120] The UE may determine the number of bits of a predetermined field (e.g., a PTRS-DMRS association field / antenna port field) included in the DCI based on the number of ranks or layers of the PUSCH. Alternatively, the UE may determine whether the PTRS-DMRS association is indicated by only the bits (or code points) of the PTRS-DMRS association field or by using the bits of the PTRS-DMRS association field and other information (e.g., bits of other fields) based on the number of ranks or layers of the PUSCH.

[0121] For example, if the number of ranks / layers of the PUSCH is greater than a predetermined number, the size of the PTRS-DMRS association field may be changed. Alternatively, if the number of ranks / layers of the PUSCH is greater than a predetermined number, the association between the PTRS and the DMRS may be indicated by a combination of the PTRS-DMRS association field and other information.

[0122] In the following description, the MSB of a field may be read as the first bit, and the LSB may be read as the second bit.

[0123] In the following description, eight ranks / layers will be mainly used as an example of ranks / layers that are greater than the predetermined value, but the number of applicable ranks / layers is not limited to this. This embodiment may also be similarly applied when five or more ranks / layers are applied.

[0124] First Embodiment In the first embodiment, a case will be described in which only one port of PTRS (or only one port as a PTRS port) is configured for a PUSCH having a rank greater than 4 (for example, rank 5-8).

[0125] The first embodiment may be suitably applied to a fully coherent PUSCH (e.g., a full-coherent PUSCH) having a rank of 5 to 8. Of course, the present invention is not limited to this, and may also be applied to a partially coherent / non-coherent PUSCH (e.g., a partial-coherent / non-coherent PUSCH).

[0126] The UE may assume that for a PUSCH (e.g., each DMRS port) having a rank greater than 4 (e.g., rank 5-8), only one port of PTRS (or only one port as a PTRS port) is configured.

[0127] In this case, at least one of the following options 1-1 to 1-2 may be applied as the size of the PTRS-DMRS association field (e.g., the PTRS-DMRS association field).

[0128] [Option 1-1] The size of the PTRS-DMRS related field may be 2 bits. By setting it to 2 bits, the size of the PTRS-DMRS related field can be made the same as that of the existing system (e.g., Rel. 17 or earlier), and an increase in DCI overhead can be suppressed.

[0129] In this case, at least one of the following options 1-1-1 to 1-1-4 may be applied.

[0130] [Option 1-1-1] The RRC / MAC CE may select / configure up to four values ​​in a table to hold two bits of the PTRS-DMRS related field. The table may be interpreted as an association / mapping between values ​​(or codepoints) of the PTRS-DMRS related field and DMRS ports.

[0131] [Option 1-1-2] At least one DCI field (e.g., a field other than the PTRS-DMRS related field) may be used together with the two-bit PTRS-DMRS related field, and the DCI may be in a predetermined DCI format (e.g., DCI format 0_1 / 0_2).

[0132] The 1-bit DCI field may be, for example, a field related to an antenna port (see Figures 10A and 10B). Figure 10A shows an example of the number of bits of the antenna port field (here, 4 bits) and the PTRS-DMRS related field (here, 2 bits) in the first rank (e.g., ranks 1 to 4). Figure 10B shows an example of the number of bits of the antenna port field (here, 3 bits) and the PTRS-DMRS related field (here, 3 bits) in the second rank (e.g., ranks 5 to 8).

[0133] The UE may switch between applying Figures 10A and 10B based on the rank number. The UE may determine the rank number based on the rank / layer indicated by the DCI. For example, the UE may assume that the size of the PTRS-DMRS-related field is 2 bits (+ the antenna port field is 4 bits) when the rank of the PUSCH is 1-4, and determine that the size of the PTRS-DMRS-related field is extended (e.g., the size of the PTRS-DMRS-related field is 3 bits (+ the antenna port field is 3 bits)) when the rank of the PUSCH is greater than 4.

[0134] In this way, when the rank is greater than 4, one bit of the antenna port field may be used for the PTRS-DMRS related field.

[0135] Here, since the four bits for the antenna port field become redundant for ranks 5 to 8, the number of bits in the antenna port field is reduced and the reduced bits are used for other purposes (here, PTRS-DMRS related fields). The number of bits in the antenna port field for ranks > X may be defined by specification or may be set by RRC parameters. For example, for ranks 1, 2, ..., X, the size of the antenna port field may be Y bits, and for ranks X+1, X+2, ..., 8, the size of the antenna port field may be Y-M bits. X, Y, and M may be predefined or set by RRC parameters.

[0136] [Option 1-1-3] The 2-bit PTRS-DMRS association field may be mapped only to a DMRS port associated with a specific CW (e.g., 1 CW). The 1 CW (e.g., the 1st CW or the 2nd CW) may be selected based on a predetermined condition. The associated CW may be predefined or configured by an RRC parameter.

[0137] [Option 1-1-4] The DCI may indicate only PTRS-DMRS associations for some PTRS ports, such as PTRS port #0. For other ports, PTRS-DMRS associations may be predefined or indicated by RRC parameters.

[0138] [Option 1-2] The size of the PTRS-DMRS association field may be more than 2 bits (e.g., 3 bits). In this case, the table shown in Fig. 11 may be applied as the PTRS-DMRS association for UL PTRS port #0. The table may be interpreted as an association / mapping between the value (or code point) of the PTRS-DMRS association field and the DMRS port.

[0139] <Second Embodiment> The second embodiment describes a case where multiple (or more than one) PTRS ports are configured for a PUSCH having a rank greater than 4 (e.g., rank 5-8). The second embodiment may be applied in combination with the first embodiment. Furthermore, the number of configured / applied PTRS ports (e.g., 1, 2, or 4) may be configured / instructed by an RRC parameter / DCI.

[0140] The second embodiment may be suitably applied to a partially coherent / non-coherent PUSCH (e.g., a partial-coherent / non-coherent PUSCH) having a rank of 5-8 (or 2 CW). Of course, the present invention is not limited to this, and may also be applied to a fully coherent PUSCH (e.g., a full-coherent PUSCH).

[0141] The UE may assume multiple (or more than one) PTRS ports are configured for a PUSCH (e.g., each DMRS port) with a rank greater than 4 (e.g., ranks 5-8). The number of PTRS ports may be configured based on the UE capability report for the antenna coherence group (Ng) = {1, 2, 4}.

[0142] In this case, at least one of the following options 2-1 to 2-2 may be applied as the size of the PTRS-DMRS association field (e.g., the PTRS-DMRS association field).

[0143] [Option 2-1] The size of the PTRS-DMRS related field may be 2 bits. In this case, at least one of the above-mentioned options 1-1-1 to 1-1-4 may be applied.

[0144] [Option 2-2] The size of the PTRS-DMRS related field may be configured to be more than 2 bits (for example, 3 bits).

[0145] The size of the PTRS-DMRS related field may be determined based on at least one of the number of PTRS ports, the antenna coherence group (e.g., reported Ng), the precoder coherence type, and codebook / non-codebook based UL MIMO. Alternatively, the size of the PTRS-DMRS related field may be directly (or explicitly) indicated by an RRC parameter (see FIG. 12).

[0146] For example, in Fig. 12, the size of the PTRS-DMRS related field corresponding to each number of PTRS ports may be defined / set based on the number of antenna coherence groups. The size of the PTRS-DMRS related field may be defined / set commonly for each antenna coherence type (1, 2, 4), or different values ​​may be defined / set.

[0147] Alternatively, when multiple panels (e.g., panels where simultaneous transmission is applied) are used for UL transmission (STxMP), the first panel may correspond to the DMRS ports associated with layers 1-4 (or 1st CW), and the second panel may correspond to the DMRS ports associated with layers 5-8 (or 2nd CW).

[0148] Alternatively, different operations may be applied between Simultaneous Transmission across Multiple Panels (STxMP) and 8Tx. For example, up to four layers (e.g., up to four DMRS ports) may be applied / supported in STxMP, and up to eight layers (e.g., up to eight DMRS ports) may be applied / supported in 8Tx.

[0149] Third Embodiment In a third embodiment, an example of a correspondence relationship between a PTRS port, a PUSCH antenna port, and a DMRS port will be described. The third embodiment may be applied in combination with the first embodiment or the second embodiment.

[0150] For partially coherent and non-coherent UEs, if the UE's antenna layout is assumed to have four antenna groups, each group consisting of coherent antennas, and the antennas are non-coherent between groups, it is also assumed that the configured maximum PTRS ports will support a predetermined value greater than two (e.g., 4).

[0151] For codebook-based UL transmission, the actual number of UL PTRS ports may be determined based on the number of TPMIs / layers. For example, PUSCH antenna ports #1000 and #1004 at the designated TPMI may share PTRS port #0, PUSCH antenna ports #1001 and #1005 at the designated TPMI may share PTRS port #1, PUSCH antenna ports #1002 and #1006 at the designated TPMI may share PTRS port #2, and PUSCH antenna ports #1003 and #1007 at the designated TPMI may share PTRS port #3.

[0152] In this case, it is also assumed that a 4-bit PTRS-DMRS association field is required to indicate the pair association between the PTRS port and the DMRS port (see Figure 13A).

[0153] If two antenna groups are assumed in the UE's antenna layout, the maximum configured PTRS ports is 2, and the actual number of UL PTRS ports may be determined based on the number of TPMIs / layers. For example, PUSCH antenna ports #1000, #1002, #1004, and #1006 in the indicated TPMI may share PTRS port #0, and PUSCH antenna ports #1001, #1003, #1005, and #1007 in the indicated TPMI may share PTRS port #1.

[0154] In this case, it is also assumed that a 4-bit PTRS-DMRS association field is required to indicate the pair association between the PTRS port and the DMRS port (see Figure 13B).

[0155] For non-codebook based UL transmission, the actual number of UL PTRS ports to be transmitted may be determined based on the SRS in DCI format 0_1 ​​or an RRC parameter (e.g., sri-ResourceIndicator in rrc-ConfiguredUplinkGrant).

[0156] When the number of PTRSs associated with a PUSH (or each DMRS) is a predetermined number (e.g., 1, 2, or 4), the association of PTRS ports shared by the DMRS port (or PUSH antenna port), and PTRS port / DMRS port / PUSH antenna port may be controlled based on at least one of the following options 3-1 to 3-3.

[0157] [Option 3-1] When one PTRS port is configured for a PUSCH with a rank greater than 4 (for example, for each DMRS port), the DMRS ports sharing the PTRS port may mean the following:

[0158] When one port of PTRS is configured for a PUSH having more than four layers (e.g., at least one of five layers, six layers, seven layers, and eight layers), PUSH antenna ports #1000, #1001, #1002, #1003, #1004, #1005, #1006, and #1007 in the indicated TPMI (or indicated by the TPMI) may share PTRS port #0.

[0159] UL PTRS port #0 may be associated with UL layer x of the layers transmitted on PUSCH antenna ports #1000, #1001, #1002, #1003, #1004, #1005, #1006, and #1007 in the indicated TPMI, where x may be given by the DCI parameter (PTRS-DMRS association) in the DCI (e.g., DCI format 0_1 / 0_2).

[0160] 14 shows an example of the correspondence relationship between DMRS ports, PUSCH antenna ports, and PTRS ports when PUSCH transmission of eight layers is assumed. The UE may be instructed by the TPMI that layers 0, 1, 2, 3, 4, 5, 6, and 7 are transmitted on PUSCH antenna ports #1000, #1001, #1002, #1003, #1004, #1005, #1006, and #1007, respectively. The UE may also determine that the DMRS ports for layers 0, 1, 2, 3, 4, 5, 6, and 7 share PTRS port #0.

[0161] <<Variations>> In Fig. 14, any DMRS port may be associated with PTRS port #0. For example, applicable DMRS port indices (e.g., DMRS ports corresponding to PTRS port #0) may be restricted. Restricting applicable DMRS port indices (e.g., restricting PTRS port #0 to only DMRS ports #0-#3) can reduce the number of PTRS-DMRS related fields. The applicable DMRS port indices may be defined in the specifications or may be set by RRC parameters.

[0162] <<Size of the PTRS-DMRS Association Field>> When one PTRS port is configured for PUSCHs with a rank greater than 4 (e.g., for each DMRS port), the size of the PTRS-DMRS association field may be 3 bits. Figure 15 shows an example of association between values ​​(or code points) of the PTRS-DMRS association field and DMRS ports.

[0163] Figure 15 shows an example of the association (for example, a table) between the value of the PTRS-DMRS related field (or code point) and the DMRS port when assuming a PUSCH of rank 8. Not limited to this, the table of Figure 15 (for example, a part) may be used for PUSCHs of ranks 5 to 7, or a table different from that of Figure 15 may be set.

[0164] Alternatively, the size of the PTRS-DMRS related field may be 2 bits. In this case, at least one of the following options 3-1-1 to 3-1-4 may be applied.

[0165] [Option 3-1-1] The RRC / MAC CE may select / instruct some values / rows (e.g., some of the eight values / rows) in the table of Figure 15 to hold two bits of the PTRS-DMRS related field. In the present disclosure, a value / row may be read as an entry.

[0166] [Option 3-1-2] One or two bits of the DCI field (for example, a field other than the PTRS-DMRS-related field) may be used in combination with two bits of the PTRS-DMRS-related field. That is, one or two bits of a field other than the PTRS-DMRS-related field may be used as the PTRS-DMRS-related field. This allows the total number of bits used in the PTRS-DMRS-related field to be three or four.

[0167] For example, two bits in the antenna port field can be used to make a total of four bits, and one bit in the antenna port field can be used to make a total of three bits.

[0168] Option 3-1-1 and Option 3-1-2 may be applied in combination.

[0169] [Option 3-1-3] The 2-bit PTRS-DMRS association field may be mapped only to a DMRS port associated with a specific CW (e.g., 1 CW). The 1 CW (e.g., the 1st CW or the 2nd CW) may be selected based on a predetermined condition. The associated CW may be predefined or configured by an RRC parameter.

[0170] [Option 3-1-4] The DCI may indicate only PTRS-DMRS associations for some PTRS ports, such as PTRS port #0. For other ports, PTRS-DMRS associations may be predefined or indicated by RRC parameters.

[0171] [Option 3-2] When two PTRS ports are configured for a PUSCH (e.g., each DMRS port) with a rank greater than 4, DMRS ports sharing a PTRS port may mean the following:

[0172] When two PTRS ports are configured for a PUSCH having more than four layers (e.g., at least one of five layers, six layers, seven layers, and eight layers), PUSCH antenna ports #1000, #1002, #1004, and #1006 in the indicated TPMI (or indicated by the TPMI) may share PTRS port #0, and PUSCH antenna ports #1001, #1003, #1005, and #1007 may share PTRS port #1.

[0173] UL PTRS port #0 may be associated with UL layer x of the layers transmitted on PUSCH antenna ports #1000, #1002, #1004, and #1006 in the indicated TPMI, and UL PTRS port #1 may be associated with UL layer y of the layers transmitted on PUSCH antenna ports #1001, #1003, #1005, and #1007 in the indicated TPMI, where at least one of x and y may be provided by a DCI parameter (PTRS-DMRS association) in the DCI (e.g., DCI format 0_1 / 0_2).

[0174] 16 shows an example of the correspondence relationship between DMRS ports, PUSCH antenna ports, and PTRS ports assuming eight-layer PUSCH transmission. The UE may be instructed by the TPMI that layers 0, 1, 2, 3, 4, 5, 6, 7, and 8 are transmitted on PUSCH antenna ports #1000, #1001, #1002, #1003, #1004, #1005, #1006, and #1007, respectively. The UE may then determine that the DMRS ports for layers 0, 2, 4, and 6 share PTRS port #0, and that the DMRS ports for layers 1, 3, 5, and 7 share PTRS port #1.

[0175] 16, any DMRS port may be associated with PTRS port #0 / #1. For example, applicable DMRS port indices (e.g., DMRS ports corresponding to PTRS port #0 / #1) may be restricted. Restricting applicable DMRS port indices can reduce the number of PTRS-DMRS related fields. The applicable DMRS port indices may be defined in the specifications or configured by RRC parameters.

[0176] 16, the association between the PUSCH antenna port and the PTRS port is an example and is not limited to this. The association between the PUSCH antenna port and the PTRS port may be defined by specification or may be set / updated by an RRC parameter.

[0177] <<Size of the PTRS-DMRS Association Field>> When two PTRS ports are configured for a PUSCH with a rank greater than four (e.g., for each DMRS port), the size of the PTRS-DMRS association field may be 4 bits. Figure 17 shows an example of association between values ​​(or code points) of the PTRS-DMRS association field and DMRS ports.

[0178] Figure 17 shows an example of the association (for example, a table) between the value of the PTRS-DMRS related field (or code point) and the DMRS port when assuming a PUSCH of rank 8. Not limited to this, the table of Figure 17 (for example, a part thereof) may be used for PUSCHs of ranks 5 to 7, or a table different from that of Figure 17 may be set.

[0179] Alternatively, the size of the PTRS-DMRS related field may be 3 bits or less (for example, 2 bits). In this case, at least one of the following options 3-2-1 to 3-2-4 may be applied.

[0180] [Option 3-2-1] The RRC / MAC CE may select / indicate some values / rows (e.g., some of the eight values / rows) in the table of Figure 17 to hold the two bits of the PTRS-DMRS related field.

[0181] [Option 3-2-2] One or two bits of the DCI field (for example, a field other than the PTRS-DMRS-related field) may be used in combination with two bits of the PTRS-DMRS-related field. That is, one or two bits of a field other than the PTRS-DMRS-related field may be used as the PTRS-DMRS-related field. This allows the total number of bits used for the PTRS-DMRS-related field to be three or four.

[0182] For example, two bits of the antenna port field can be used to make it four bits in total. One bit of the antenna port field can be used to make it three bits in total. In this case, the remaining one bit may be secured using another method (e.g., option 3-2-1).

[0183] [Option 3-2-3] The 2-bit PTRS-DMRS association field may be mapped only to a DMRS port associated with a specific CW (e.g., 1 CW). The 1 CW (e.g., the 1st CW or the 2nd CW) may be selected based on a predetermined condition. The associated CW may be predefined or configured by an RRC parameter.

[0184] [Option 3-2-4] The DCI may indicate only PTRS-DMRS associations for some PTRS ports, such as PTRS port #0. For other ports, PTRS-DMRS associations may be predefined or indicated by RRC parameters.

[0185] [Option 3-3] When four PTRS ports are configured for a PUSCH with a rank greater than four (e.g., each DMRS port), DMRS ports sharing a PTRS port may mean the following:

[0186] When four PTRS ports are configured for a PUSCH having more than four layers (e.g., at least one of five layers, six layers, seven layers, and eight layers), PUSCH antenna ports #1000 and #1002 in the indicated TPMI (or indicated by the TPMI) may share PTRS port #0. PUSCH antenna ports #1001 and #1003 may share PTRS port #1. PUSCH antenna ports #1004 and #1006 may share PTRS port #2. PUSCH antenna ports #1005 and #1007 may share PTRS port #3.

[0187] UL PTRS port #0 may be associated with UL layer x of the layer transmitted on PUSCH antenna ports #1000 and #1002 in the indicated TPMI, UL PTRS port #1 may be associated with UL layer y of the layer transmitted on PUSCH antenna ports #1001 and #1003 in the indicated TPMI, UL PTRS port #2 may be associated with UL layer z of the layer transmitted on PUSCH antenna ports #1004 and #1006 in the indicated TPMI, and UL PTRS port #3 may be associated with UL layer o of the layer transmitted on PUSCH antenna ports #1005 and #1007 in the indicated TPMI. Here, at least one of x, y, z, and o may be given by a DCI parameter (PTRS-DMRS association) in the DCI (for example, DCI format 0_1 / 0_2).

[0188] 18 shows an example of the correspondence relationship between DMRS ports, PUSCH antenna ports, and PTRS ports when PUSCH transmission of eight layers is assumed. The UE may be instructed by the TPMI that layers 0, 1, 2, 3, 4, 5, 6, 7, and 8 are transmitted on PUSCH antenna ports #1000, #1001, #1002, #1003, #1004, #1005, #1006, and #1007, respectively. The UE may also determine that the DMRS ports for layers 0 and 2 share PTRS port #0, the DMRS ports for layers 1 and 3 share PTRS port #1, the DMRS ports for layers 4 and 6 share PTRS port #2, and the DMRS ports for layers 5 and 7 share PTRS port #3.

[0189] <<Variations>> In FIG. 18 , any DMRS port may be associated with PTRS port #0 / #1 / #2 / #3. For example, applicable DMRS port indices (e.g., DMRS ports corresponding to PTRS port #0 / #1 / #2 / #3) may be restricted. Restricting applicable DMRS port indices can reduce the number of PTRS-DMRS related fields. The applicable DMRS port indices may be defined in the specifications or configured by RRC parameters.

[0190] 18, the association between the PUSCH antenna port and the PTRS port is an example and is not limited to this. The association between the PUSCH antenna port and the PTRS port may be defined by specification or may be set / updated by an RRC parameter.

[0191] <<Size of the PTRS-DMRS Association Field>> When four PTRS ports are configured for a PUSCH with a rank greater than four (e.g., each DMRS port), the size of the PTRS-DMRS association field may be 4 bits. Figure 19 shows an example of association between values ​​(or code points) of the PTRS-DMRS association field and DMRS ports.

[0192] Figure 19 shows an example of the association (for example, a table) between the value of the PTRS-DMRS related field (or code point) and the DMRS port when assuming a PUSCH of rank 8. Not limited to this, the table of Figure 19 (for example, a part) may be used for PUSCHs of ranks 5 to 7, or a table different from that of Figure 19 may be set.

[0193] Alternatively, the size of the PTRS-DMRS related field may be 3 bits or less (for example, 2 bits). In this case, at least one of the following options 3-3-1 to 3-3-4 may be applied.

[0194] [Option 3-3-1] The RRC / MAC CE may select / indicate some values / rows (e.g., some of the eight values / rows) in the table of Figure 19 to hold the two bits of the PTRS-DMRS related field.

[0195] [Option 3-3-2] One or two bits of the DCI field (for example, a field other than the PTRS-DMRS-related field) may be used in combination with two bits of the PTRS-DMRS-related field. That is, one or two bits of a field other than the PTRS-DMRS-related field may be used as the PTRS-DMRS-related field. This allows the total number of bits used in the PTRS-DMRS-related field to be three or four.

[0196] For example, two bits of the antenna port field can be used to make it four bits in total. One bit of the antenna port field can be used to make it three bits in total. In this case, the remaining one bit may be secured using another method (e.g., option 3-2-1).

[0197] [Option 3-3-3] The 2-bit PTRS-DMRS association field may be mapped only to a DMRS port associated with a specific CW (e.g., 1 CW). The 1 CW (e.g., the 1st CW or the 2nd CW) may be selected based on a predetermined condition. The associated CW may be predefined or configured by an RRC parameter.

[0198] [Option 3-3-4] The DCI may indicate only PTRS-DMRS associations for some PTRS ports, such as PTRS port #0. For other ports, PTRS-DMRS associations may be predefined or indicated by RRC parameters.

[0199] <Variations> The PTRS-DMRS related field applied in the first, second, and third embodiments may be an extension of the PTRS-DMRS related field of an existing system (see FIG. 20A), or may be a field to which a new field (e.g., a second field / additional field) is added (see FIG. 20B).

[0200] Figure 20A shows an example of a case where one PTRS-DMRS-related field (e.g., size) is extended. Figure 20B shows an example of a case where a new field (e.g., 2nd field) is added to the PTRS-DMRS-related field.

[0201] The extension of the PTRS-DMRS related field may be based on higher layer configuration, for example, for rank 5-8 PUSCH, the application of an extended PTRS-DMRS related field (e.g., a total of 4 bits) may be supported.

[0202] On the other hand, for rank 1-4 PUSCH, only a part of the extended PTRS-DMRS-associated field may be applied. For example, when applying Figure 20A, only the two MSB / LSB bits of the PTRS-DMRS-associated field are used, and the other bits of the PTRS-DMRS-associated field may be ignored or used for other purposes. When applying Figure 20B, only the first PTRS-DMRS-associated field (2 bits) is used, and the second PTRS-DMRS-associated field may be ignored or used for other purposes.

[0203] The first, second, and third embodiments may be applied to / supported for simultaneous transmission across multiple panels (STxMP). In STxMP, when two panels are applied (e.g., when there are two indicated TCI states / when the SDM rank is greater than 1), a total of four bits are required. On the other hand, when one panel is applied (e.g., when there is one indicated TCI state / when the SDM rank is 1), a total of two bits are required. When two panels are applied, the extended PTRS-DMRS-related field is applied, and when one panel is applied, only a part of the extended PTRS-DMRS-related field may be applied.

[0204] <Supplementary Information> [Notification of Information to UE] In the above-described embodiments, any information may be notified to the UE (from a network (NW) (e.g., a base station (BS))) (in other words, reception of any information from the BS by the UE) using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0205] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not defined in existing standards.

[0206] When the 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 Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

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

[0208] [Notification of Information from UE] In the above-described embodiments, notification of any information from the UE (to the NW) (in other words, transmission / report 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), a specific signal / channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.

[0209] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new LCID, which is not defined in existing standards, in the MAC subheader.

[0210] If the notification is made by UCI, the notification may be transmitted using PUCCH or PUSCH.

[0211] Furthermore, any information in the above-described embodiments may be notified from the UE periodically, semi-persistently, or aperiodically.

[0212] [Application of Each Embodiment] At least one of the above-described embodiments may be applied when a specific condition is met. The specific condition may be defined in a standard or may be notified to a UE / BS using higher layer signaling / physical layer signaling.

[0213] At least one of the above-described embodiments may be applied only to UEs that have reported or support a particular UE capability.

[0214] The specific UE capabilities may indicate at least one of the following: - Supporting specific processing / operation / control / information for at least one of the above embodiments, - Supporting PUSCH with more than four ranks, - Supporting Rel. 15 / 16 / 17 DMRS ports / Rel. 18 DMRS ports, - Supporting more than one (or two) PTRS ports for PUSCH with more than four ranks, - Supporting PTRS-DMRS association indication in DCI (e.g., DCI format 0_1 / 0_2) (if not supported, PTRS-DMRS association may be indicated only by RRC / MAC CE).

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

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

[0217] At least one of the above-described embodiments may also be applied when the UE configures / activates / triggers specific information related to the above-described embodiments (or performs the operations of the above-described embodiments) through higher layer / physical layer signaling, such as information indicating enabling switching between single-TRP and multi-TRP when using unified TCI state, or any RRC parameter for a specific release (e.g., Rel. 18 / 19), etc.

[0218] If the UE does not support at least one of the specific UE capabilities or is not configured with the specific information, the UE may apply, for example, the behavior of Rel. 15 / 16 / 17.

[0219] (Supplementary Notes) The following inventions are supplementary notes regarding one embodiment of the present disclosure. [Supplementary Note 1] A terminal comprising: a receiver that receives downlink control information including a field that indicates an association between a uplink phase tracking reference signal (PTRS) and a demodulation reference signal (DMRS) for an uplink shared channel (PUSCH); and a controller that determines the association between the PTRS and the DMRS based on the field, wherein, when the number of ranks or layers of the PUSCH is greater than a predetermined number, the size of the field changes, or the association between the PTRS and the DMRS is indicated by a combination of the field and other information. [Supplementary Note 2] The terminal according to Supplementary Note 1, in which, when the number of ranks or layers of the PUSCH is greater than a predetermined number, one PTRS port is configured for the PUSCH. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, in which, when the number of ranks or layers of the PUSCH is greater than a predetermined number, multiple PTRS ports are configured for the PUSCH. [Supplementary Note 4] A terminal according to any one of Supplementary Notes 1 to 3, wherein when the number of PTRS ports is set to four, each bit of the field indicates a DMRS port that shares each of the four PTRS ports.

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

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

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

[0223] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (Master Node (MN)), and the NR base station (gNB) is the secondary node (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.

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

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

[0226] 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 (CCs) and dual connectivity (DC).

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

[0228] Furthermore, the user terminal 20 may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

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

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

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

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

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

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

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

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

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

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

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

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

[0241] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," "CORESET configuration," and the like in the present disclosure may be read interchangeably.

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

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

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

[0245] 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 an SS (PSS, SSS) and a PBCH (and a DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as a reference signal.

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

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

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

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

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

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

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

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

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

[0255] The transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

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

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

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

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

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

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

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

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

[0264] The transceiver 120 may transmit downlink control information including a field indicating an association between a uplink phase tracking reference signal (PTRS) and a demodulation reference signal (DMRS) for a physical uplink shared channel (PUSCH).

[0265] The control unit 110 may instruct the association between the PTRS and the DMRS based on the field. Furthermore, when the rank number or the number of layers of the PUSCH is greater than a predetermined value, the control unit 110 may change the size of the field or instruct the association between the PTRS and the DMRS by combining the field with other information.

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

[0267] In this example, the functional blocks of the characteristic parts of the present 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 unit described below may be omitted.

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

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

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

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

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

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

[0274] The transceiver unit 220 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0275] The transceiver 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, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

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

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

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

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

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

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

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

[0283] The transceiver 220 may receive downlink control information including a field indicating an association between a uplink phase tracking reference signal (PTRS) and a demodulation reference signal (DMRS) for a physical uplink shared channel (PUSCH).

[0284] The control unit 210 may determine the association between the PTRS and the DMRS based on the field. If the rank number or the number of layers of the PUSCH is greater than a predetermined number, the size of the field may be changed, or the association between the PTRS and the DMRS may be indicated by a combination of the field and other information.

[0285] When the number of ranks or layers of the PUSCH is greater than a predetermined number, the configuration of one (e.g., only one) PTRS port for the PUSCH may be supported. Alternatively, when the number of ranks or layers of the PUSCH is greater than a predetermined number, the configuration of multiple PTRS ports for the PUSCH may be supported.

[0286] When the number of PTRS ports is set to four, each bit of the field may indicate a DMRS port that shares each of the four PTRS ports.

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

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

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

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

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

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

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

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

[0295] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EEPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, cache, main memory, etc. The memory 1002 may store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0315] In addition, one or more RBs may be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

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

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

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

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

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

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

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

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

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

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

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

[0327] Note that the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be referred to as an RRC message, such as an RRC Connection Setup message or an RRC Connection Reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0342] 25 is a diagram showing an example of a vehicle according to an 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, axles 48, an electronic control unit 49, various sensors (including a current sensor 50, an RPM sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

A receiving unit that receives downlink control information (DCI) including a field indicating an association between one or more uplink phase tracking reference signal (UL PTRS) ports and one or more demodulation reference signal (DMRS) ports for physical uplink shared channel (PUSCH) transmission; A control unit that determines the association between the one or more UL PTRS ports and the one or more DMRS ports based on the field; and A terminal, wherein when the PUSCH transmission is multi-panel simultaneous transmission, the maximum number of the one or more DMRS ports is 4, and when the PUSCH transmission is transmission by more than 4 ranks or layers, the maximum number of the one or more DMRS ports is 8. A step of receiving downlink control information (DCI) including a field indicating an association between one or more uplink phase tracking reference signal (UL PTRS) ports and one or more demodulation reference signal (DMRS) ports for physical uplink shared channel (PUSCH) transmission; A step of determining the association between the one or more UL PTRS ports and the one or more DMRS ports based on the field; and A wireless communication method for a terminal, wherein when the PUSCH transmission is multi-panel simultaneous transmission, the maximum number of the one or more DMRS ports is 4, and when the PUSCH transmission is transmission by more than 4 ranks or layers, the maximum number of the one or more DMRS ports is 8. A transmitting unit that transmits downlink control information (DCI) including a field indicating an association between one or more uplink phase tracking reference signal (UL PTRS) ports and one or more demodulation reference signal (DMRS) ports for physical uplink shared channel (PUSCH) transmission; A control unit that indicates the association between the one or more UL PTRS ports and the one or more DMRS ports based on the field; and A base station, wherein when the PUSCH transmission is multi-panel simultaneous transmission, the maximum number of the one or more DMRS ports is 4, and when the PUSCH transmission is transmission by more than 4 ranks or layers, the maximum number of the one or more DMRS ports is 8. A system having a terminal and a base station, wherein the terminal A receiving unit that receives downlink control information (DCI) including a field for indicating the association between one or more uplink phase tracking reference signal (UL PTRS) ports and one or more demodulation reference signal (DMRS) ports for physical uplink shared channel (PUSCH) transmission; A control unit that determines the association between the one or more UL PTRS ports and the one or more DMRS ports based on the field; The base station has a transmitting unit that transmits the DCI; A system in which when the PUSCH transmission is multi-panel simultaneous transmission, the maximum number of the one or more DMRS ports is 4, and when the PUSCH transmission is transmission by more than 4 ranks or layers, the maximum number of the one or more DMRS ports is 8.