PT-RS extension for more DMRS ports

Abstract

In one embodiment, a method performed by a user equipment (UE) includes, for each of one or more resource blocks (RBs) assigned for a configured phase tracking reference signal (PT-RS) port, determining a PT-RS subcarrier offset for the PT-RS port from a table based on a demodulation reference signal (DMRS) port associated with the PT-RS port, a DMRS configuration type, and a resource element offset parameter configured for the UE. The associated DMRS port is one of a plurality of DMRS ports. Each row of the table is associated with one DMRS port and specifies different PT-RS subcarrier offsets for the PT-RS port associated with that DMRS port for different resource element offset parameter values ​​for at least one DMRS configuration type. The method further includes, for each of the assigned RBs, transmitting / receiving a PT-RS on the PT-RS port in the RB according to the determined PT-RS subcarrier offset.

Description

[Technical Field]

[0001] Related Applications This application claims the benefit of Provisional Patent Application No. 63 / 432,956, filed December 15, 2022, the entire disclosure of which is incorporated herein by reference.

[0002] The present disclosure relates to wireless communication systems, and more particularly to phase tracking reference signals (PT-RS) in wireless communication systems. [Background technology]

[0003] The 3rd Generation Partnership Project (3GPP) New Radio (NR) uses cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) in both the downlink (DL) (i.e., from the network node, gNB, or base station, to the user equipment or UE) and uplink (UL) (i.e., from the UE to the gNB). Discrete Fourier transform (DFT) spread orthogonal frequency division multiplexing (OFDM) is also supported in the uplink. In the time domain, the NR downlink and uplink are each organized into equal-sized subframes of 1 millisecond (ms). The subframes are further divided into multiple slots of equal duration. The slot length depends on the subcarrier spacing. For a subcarrier spacing of Δf = 15 kilohertz (kHz), there is only one slot per subframe, and each slot consists of 14 OFDM symbols.

[0004] Data scheduling in NR is generally slot-based, and an example with a 14-symbol slot is shown in FIG. 1A, where the first two symbols contain the Physical Downlink Control Channel (PDCCH) and the rest of the symbols contain the Physical Shared Data Channel, i.e., either the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH).

[0005] Various subcarrier spacing (SCS) values ​​are supported in NR. The supported SCS values ​​(also called various numerologies) are given by Δf = (15 × 2^μ) kHz, where μ ∈ {0, 1, 2, 3, 4}. Δf = 15 kHz is the basic subcarrier spacing. The slot duration for a given subcarrier spacing is 1 / 2^μms.

[0006] In the frequency domain, the system bandwidth is divided into resource blocks (RBs), each corresponding to 12 adjacent subcarriers. RBs are numbered starting with 0 from one end of the system bandwidth. The basic NR physical time-frequency resource grid is shown in Figure 1B, where only one RB in a 14-symbol slot is shown. One OFDM subcarrier in one OFDM symbol interval forms one resource element (RE).

[0007] Downlink transmissions to a user equipment (UE) can be dynamically scheduled by sending downlink control information (DCI) with a DL DCI format on a PDCCH. The DCI includes scheduling information such as time and frequency resources, modulation and coding schemes, etc. User data is carried on a PDSCH. The UE first detects and decodes the PDCCH, and if successful, the UE then decodes the corresponding PDSCH according to the scheduling information in the DCI.

[0008] Similarly, uplink data transmissions can be dynamically scheduled using the UL DCI format on the PDCCH. The UE first decodes the uplink grant in the DCI and then transmits data on the PUSCH according to the control information included in the uplink grant, such as modulation order, coding rate, and uplink resource allocation.

[0009] NR PT-RS In NR, a phase tracking reference signal (PT-RS or PTRS) can be configured for downlink and uplink transmissions to allow the receiver to correct phase noise-related errors. The PT-RS configuration is UE-specific, and the PT-RS is associated with one of the demodulation reference signal (DMRS) ports used for PDSCH or PUSCH transmissions. This means that the DMRS and its associated PT-RS are transmitted using the same precoder. Therefore, no matter what DMRS sequence is configured, the modulated symbols used for the PT-RS are taken from the DMRS. This means that there is no specific configuration for the PT-RS sequence, since it borrows from the DMRS.

[0010] In the DL, if the UE is scheduled with one codeword, the PT-RS antenna port is associated with the lowest indexed DMRS antenna port among the DMRS antenna ports allocated for the PDSCH. If the UE is scheduled with two codewords, the PT-RS antenna port is associated with the lowest indexed DMRS antenna port among the DMRS antenna ports allocated for the codeword with the higher MCS. If the two codewords have the same MCS index, the PT-RS antenna port is associated with the lowest indexed DMRS antenna port allocated for codeword 0.

[0011] In the UL, for PUSCHs scheduled by DCI format 0_0 or by activated DCI format 0_0, the UL PT-RS port is associated with DMRS port 0. For PUSCHs scheduled by DCI format 0_1 ​​and DCI format 0_2, the PT-RS port to DMRS port association is dynamically indicated in the DCI and is described in clause 6.2.2 in 3GPP Technical Specification (TS) 38.214 (see, e.g., v17.3.0).

[0012] The presence of a PT-RS is indicated by Radio Resource Control (RRC) signaling independently for UL and DL. The uplink and downlink PTRS configuration in 3GPP TS38.331 v17.2.0 is shown in Figure 1C.

[0013] At most two PT-RS ports are configured per user (to support multi-panel transmission in the UL and multi-transmit and receive point (TRP) transmission in the DL). This is configured by maxNrofPorts. For Type-2 DMRS, there are a total of at most six orthogonal PT-RS ports for multi-user multiple-input multiple-output (MU-MIMO), and for Type-1 DMRS, there may be a total of four orthogonal PT-RS ports. PT-RS ports are precoded on the antenna port using the same precoder of the associated DMRS port. PT-RSs are not mapped to resource elements used for DMRS, synchronization signal blocks (SSBs), channel state information reference signals (CSI-RS), etc.

[0014] For CP-OFDM, the supported time and frequency densities for PT-RS include: Time density: 1, 1 / 2, and 1 / 4 (i.e., one PT-RS symbol per symbol, every two symbols, and every four OFDM symbols, respectively) Frequency density: 1 / 2 and 1 / 4 (i.e., one PTRS subcarrier per two and four physical resource blocks (PRBs), respectively)

[0015] The time density and frequency density are associated with DCI parameters, such as modulation coding scheme (MCS) and scheduled bandwidth (BW), and are specified by clause 5.1.6.3 in 3GPP TS38.214 v17.2.0 for DL ​​and clause 6.2.3 in 3GPP TS38.214 v17.2.0 for UL.

[0016] The PT-RS is restricted in the scheduling RB. The RB containing the PT-RS is derived as follows: For DL / UL unicast transmission, the RB level offset is implicitly derived from the UE's Radio Network Temporary Identifier (RNTI) and frequency density. The PT-RS is mapped on one DMRS subcarrier of the associated DMRS port in each allocated RB. Also, the subcarrier used for the PT-RS port must be one of the subcarriers also used for the DM-RS port associated with the PT-RS port. The PTRS subcarrier k in the scheduled PDSCH or PUSCH RB is It is determined as TIFF2026500273000002.tif7170, where: i=0,1,2,... · TIFF2026500273000003.tif7170 is the subcarrier offset, given in Table 7.4.1.2.2-1 of 3GPP TS38.211 v17.2.0 for DL ​​and in Table 6.4.1.2.2.1-1 of 3GPP TS38.211 v17.2.0 for UL. The tables are reproduced below as Table 1 and Table 2, where resourceElementOffset is a parameter set by RRC. If resourceElementOffset is not set, the column corresponding to "offset00" shall be used. ·K PT-RS is the frequency density of PT-RS, and K PT-RS ∈{2,4}, · TIFF2026500273000004.tif7170 is the RB offset for PT-RS, Given by TIFF2026500273000005.tif13170, · TIFF2026500273000006.tif5170 is the number of subcarriers per RB, N RB is the number of scheduled RBs, n RNTI is the RNTI associated with the DCI that schedules the transmission. Within each RB allocated for a PT-RS, the subcarriers for the PT-RS, also referred to as resource element offset, are determined by both the index of the associated DMRS port and the RRC configured parameter resourceElementOffset.

[0017] Note that in the DL, the DMRS antenna ports (same for PDSCH transmission) start with port index 1000, and in the UL, the DMRS antenna ports (same for PUSCH transmission) start with 0. In NR, the same DMRS design is used for both PDSCH in the DL and PUSCH in the UL. For ease of explanation, relative DMRS numbering, i.e., DMRS ports starting with port 0, may be used for both DL and UL in the following description. In that case, it should be understood that in the DL, DMRS port k actually means DMRS port 1000+k in the DL. TIFF2026500273000007.tif67170TIFF2026500273000008.tif73170

[0018] In PT-RS time-domain mapping, the mapping starts at the first symbol containing a PDSCH / PUSCH in a slot. Then, the mapping is done every L symbols (according to the time density 1 / L). The PT-RS is not transmitted in the OFDM symbol containing the PDSCH / PUSCH DMRS. The PTRS mapping is restarted at each DMRS symbol and then mapped to this symbol. In the case of two adjacent DMRS symbols, the mapping is restarted using the second DMRS symbol as a reference.

[0019] An example of a PTRS RE in a PTRS RB is shown in Figure 1D for time domain density 1 / 2, where the PTRS port is associated with Type 1 DMRS port 1 and the RRC parameter resourceElementOffset is set as "offset10", with a single symbol DMRS in the RB on the left side of Figure 1D and a double symbol DMRS in the RB on the right side of Figure 1D.

[0020] Another example is shown in Figure 1E, where a PTRS port is associated with a single symbol type 1 DMRS port 1 (shown on the left side of Figure 1E) and a single symbol type 2 DMRS port 1 (shown on the right side of Figure 1E), both again with the RRC parameter resourceElementOffset set as "offset10", but with a PTRS time density of L=1.

[0021] For CP-OFDM, in each subcarrier allocated for PT-RS, the DMRS symbol in that subcarrier and the first frontloaded DMRS OFDM symbol before applying FD-OCC are also used for the PT-RS.

[0022] As described above, NR supports two types of DMRS for PDSCH and PUSCH: Type 1 and Type 2. The maximum number of DMRS ports for Type 1 DMRS is 4 for single-symbol DMRS and 8 for double-symbol DMRS. For Type 2 DMRS, the maximum number of DMRS ports is 6 for single-symbol DMRS and 12 for double-symbol DMRS.

[0023] DMRS ports are organized in code division multiplexing (CDM) groups. In Type 1 DMRS, there are two CDM groups, Group 0 and 1. In each RB in an OFDM symbol, CDM Group 0 is defined on the six even-numbered subcarriers, while CDM Group 1 is defined on the six odd-numbered subcarriers. In Type 2 DMRS, there are three CDM groups, each containing two pairs of REs in each RB. An example is shown in Figure 1E.

[0024] Each CDM group comprises two DMRS ports for single-symbol DMRS, and the two DMRS ports are multiplexed using a frequency-domain orthogonal cover code with length 2 (FD-OCC2). The number of DMRS ports is doubled when double-symbol DMRS is configured, where, in addition to FD-OCC2, a time-domain (TD) OCC (TD-OCC2) of length 2 is used across two OFDM symbols. Details are described in clauses 6.4.1.1 and 7.4.1.1 of 3GPP TS38.211. The relationship between DMRS ports and CDM groups for PUSCH is shown in Figure 2A for Type 1 DMRS and in Figure 2B for Type 2 DMRS. The same applies to simply using ports TIFF2026500273000009.tif5170 It can be applied to PDSCH DMRS by replacing it with TIFF2026500273000010.tif5170.

[0025] An important aspect is that PT-RS is not scheduled when using TD-OCC for DMRS. Thus, in the case of PDSCH, when using DMRS ports 1004-1007 for DMRS Type 1 and ports 1006-1011 for DMRS Type 2, the PT-RS will never be present. The same is applicable to DMRS for PUSCH.

[0026] PT-RS Power Allocation The PT-RS transmit power can be boosted when the PDSCH includes two or more spatial layers. In other words, the ratio of the PT-RS energy per resource element (EPRE) to the PDSCH EPRE (ρ PTRS ) can be greater than 0 decibels (dB). This is because in PT-RS, only a single layer is transmitted, but PDSCH can have multiple layers. For the same total EPRE, the per-layer EPRE for PT-RS can be greater than for PDSCH when PDSCH has two or more layers.

[0027] When a UE is scheduled with one or two PT-RS ports associated with a PDSCH, and when the UE is configured with the higher layer parameter epre-ratio, the ratio of PT-RS EPRE to PDSCH EPRE per layer per RE for each PT-RS port (ρ PTRS ) according to the epre-Ratio is given by Table 4.1-2 in 3GPP TS38.214 v17.2.0 (reproduced below as Table 3). Otherwise, if the higher layer parameter epre-Ratio is not configured in the UE, the UE shall assume that epre-Ratio is set to state "0" in Table 4.1-2. TIFF2026500273000011.tif51170

[0028] Similarly, the UE receives Q p ={1,2} The number of layers scheduled with (one or more) PT-RS ports TIFF2026500273000012.tif7170, PUSCH to PT-RS power ratio per layer per RE TIFF2026500273000013.tif6170 TIFF2026500273000014.tif6170, where: TIFF2026500273000015.tif6170 is shown in Table 6.2.3.1-3 of 3GPP TS38.214 v17.2.0 (reproduced here as Table 4) when the higher layer parameter ptrs-Power is set.

[0029] If the higher layer parameter ptrs-Power is not configured, the UE shall assume that ptrs-Power in PTRS-UplinkConfig is set to state "00" in Table 6.2.3.1-3 of 3GPP TS38.314. TIFF2026500273000016.tif85170

[0030] In NR Rel-18, the number of DMRS ports per CDM group will be doubled for both Type-1 and Type-2 DMRS by introducing a length-4 frequency-domain (FD) OCC code in each CDM group, as shown in Figure 2C for Type-1 DMRS and Figure 2D for Type-2 DMRS. TIFF2026500273000017.tif5170 It can be applied to PDSCH DMRS by replacing it with TIFF2026500273000018.tif5170. Summary of the Invention

[0031] Systems and methods are disclosed for a phase tracking reference signal (PT-RS) for an increased number of demodulation reference signal (DMRS) ports. In one embodiment, a method performed by a user equipment (UE) in a wireless communication system includes, for each resource block (RB) of one or more RBs assigned for a PT-RS port configured for the UE, determining a PT-RS subcarrier offset for the PT-RS port from a table based on the DMRS port associated with the PT-RS port, a DMRS configuration type, and a resource element offset parameter configured for the UE. The DMRS port associated with the PT-RS port is one of a plurality of DMRS ports, eight of the plurality of DMRS ports being associated with a first DMRS configuration type and twelve of the plurality of DMRS ports being associated with a second DMRS configuration type. Each row of the table is associated with one of the plurality of DMRS ports and specifies different PT-RS subcarrier offsets for the PT-RS port associated with one of the plurality of DMRS ports for different resource element offset parameter values ​​for at least one of the first DMRS configuration type and the second DMRS configuration type. The method further includes, for each RB of one or more RBs assigned for the PT-RS port configured for the UE, transmitting or receiving a PT-RS on the PT-RS port in the RB according to the determined PT-RS subcarrier offset. In this manner, phase tracking with the PT-RS for a Physical Downlink Shared Channel (PDSCH) or a Physical Uplink Shared Channel (PUSCH) having up to eight layers is enabled by assigning appropriate subcarrier offsets.

[0032] In one embodiment, the table is an uplink table associated with a PUSCH transmission, and one or more RBs are N RBs scheduled for PUSCH. RB In one embodiment, the plurality of DMRS ports includes DMRS ports 0 to 17, and the uplink table includes: A row associated with DMRS port 8, said row being: a PT-RS subcarrier offset of 4 for a resource offset parameter value of “00” for the first DMRS configuration type; and a PT-RS subcarrier offset of 6 for a resource offset parameter value of “01” for the first DMRS configuration type; and a PT-RS subcarrier offset of 10 for a resource offset parameter value of “10” for the first DMRS configuration type; and A PT-RS subcarrier offset of 0 for a resource offset parameter value of “11” for the first DMRS configuration type; The lines, A row associated with DMRS port 9, said row being: a PT-RS subcarrier offset of 6 for a resource offset parameter value of “00” for the first DMRS configuration type; and a PT-RS subcarrier offset of 8 for a resource offset parameter value of “01” for the first DMRS configuration type; and a PT-RS subcarrier offset of 0 for a resource offset parameter value of “10” for the first DMRS configuration type; and A PT-RS subcarrier offset of 2 for a resource offset parameter value of “11” for the first DMRS configuration type; The lines, A row associated with a DMRS port 10, said row comprising: a PT-RS subcarrier offset of 5 for a resource offset parameter value of “00” for the first DMRS configuration type; and a PT-RS subcarrier offset of 7 for a resource offset parameter value of “01” for the first DMRS configuration type; and a PT-RS subcarrier offset of 11 for a resource offset parameter value of “10” for the first DMRS configuration type; and A PT-RS subcarrier offset of 1 for a resource offset parameter value of “11” for the first DMRS configuration type; The lines, A row associated with DMRS port 11, said row being: a PT-RS subcarrier offset of 7 for a resource offset parameter value of “00” for the first DMRS configuration type; and a PT-RS subcarrier offset of 9 for a resource offset parameter value of “01” for the first DMRS configuration type; and a PT-RS subcarrier offset of 1 for a resource offset parameter value of “10” for the first DMRS configuration type; and A PT-RS subcarrier offset of 3 for a resource offset parameter value of “11” for the first DMRS configuration type; The lines, A row associated with DMRS port 12, said row comprising: a PT-RS subcarrier offset of 6 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 7 for a resource offset parameter value of “01” for the second DMRS configuration type; and a PT-RS subcarrier offset of 0 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 1 for a resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with DMRS port 13, said row comprising: a PT-RS subcarrier offset of 7 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 0 for a resource offset parameter value of “01” for the second DMRS configuration type; and a PT-RS subcarrier offset of 1 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 6 for a resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with a DMRS port 14, said row comprising: a PT-RS subcarrier offset of 8 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 9 for a resource offset parameter value of “01” for the second DMRS configuration type; and a PT-RS subcarrier offset of 2 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 3 for a resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with DMRS port 15, said row comprising: a PT-RS subcarrier offset of 9 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 2 for a resource offset parameter value of “01” for a second DMRS configuration type; and a PT-RS subcarrier offset of 3 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 8 for a resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with a DMRS port 16, said row comprising: a PT-RS subcarrier offset of 10 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 11 for a resource offset parameter value of “01” for the second DMRS configuration type; and a PT-RS subcarrier offset of 4 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 5 for a resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with DMRS port 17, said row being: a PT-RS subcarrier offset of 11 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 4 for a resource offset parameter value of “01” for the second DMRS configuration type; and a PT-RS subcarrier offset of 5 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 10 for a resource offset parameter value of “11” for the second DMRS configuration type; Defines the line and Includes.

[0033] In one embodiment, the uplink table comprises: A row associated with DMRS port 0, said row being: a PT-RS subcarrier offset of 0 for a resource offset parameter value of “00” for the first DMRS configuration type; and a PT-RS subcarrier offset of 2 for a resource offset parameter value of “01” for the first DMRS configuration type; and a PT-RS subcarrier offset of 6 for a resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 8 for a resource offset parameter value of “11” for the first DMRS configuration type; and a PT-RS subcarrier offset of 0 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 1 for a resource offset parameter value of “01” for a second DMRS configuration type; and a PT-RS subcarrier offset of 6 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 7 for a resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with DMRS port 1, said row being: a PT-RS subcarrier offset of 2 for a resource offset parameter value of “00” for the first DMRS configuration type; and a PT-RS subcarrier offset of 4 for a resource offset parameter value of “01” for the first DMRS configuration type; and a PT-RS subcarrier offset of 8 for a resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 10 for a resource offset parameter value of “11” for the first DMRS configuration type; and a PT-RS subcarrier offset of 1 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 6 for a resource offset parameter value of “01” for the second DMRS configuration type; and a PT-RS subcarrier offset of 7 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 0 for a resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with DMRS port 2, said row being: a PT-RS subcarrier offset of 1 for a resource offset parameter value of “00” for the first DMRS configuration type; and a PT-RS subcarrier offset of 3 for a resource offset parameter value of “01” for the first DMRS configuration type; and a PT-RS subcarrier offset of 7 for a resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 9 for a resource offset parameter value of “11” for the first DMRS configuration type; and a PT-RS subcarrier offset of 2 for a resource offset parameter value of “00” for a second DMRS configuration type; and a PT-RS subcarrier offset of 3 for a resource offset parameter value of “01” for the second DMRS configuration type; and a PT-RS subcarrier offset of 8 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 9 for a resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with DMRS port 3, said row being: a PT-RS subcarrier offset of 3 for a resource offset parameter value of “00” for the first DMRS configuration type; and a PT-RS subcarrier offset of 5 for a resource offset parameter value of “01” for the first DMRS configuration type; and a PT-RS subcarrier offset of 9 for a resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 11 for a resource offset parameter value of “11” for the first DMRS configuration type; and a PT-RS subcarrier offset of 3 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 8 for a resource offset parameter value of “01” for the second DMRS configuration type; and a PT-RS subcarrier offset of 9 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 2 for a resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with DMRS port 4, said row being: a PT-RS subcarrier offset of 4 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 5 for a resource offset parameter value of “01” for the second DMRS configuration type; and a PT-RS subcarrier offset of 10 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 11 for a resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with DMRS port 5, said row being: a PT-RS subcarrier offset of 5 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 10 for a resource offset parameter value of “01” for the second DMRS configuration type; and a PT-RS subcarrier offset of 11 for a resource offset parameter value of “10” for a second DMRS configuration type; and A PT-RS subcarrier offset of 4 for a resource offset parameter value of “11” for the second DMRS configuration type; Defines the line and Further includes:

[0034] In one embodiment, the table is a downlink table associated with a PDSCH transmission, and one or more RBs are N RBs scheduled for the PDSCH. RB In one embodiment, the plurality of DMRS ports includes DMRS ports 0 to 17, and the downlink table is A row associated with a DMRS port 1008, said row comprising: a PT-RS subcarrier offset of 4 for a resource offset parameter value of “00” for the first DMRS configuration type; and a PT-RS subcarrier offset of 6 for a resource offset parameter value of “01” for the first DMRS configuration type; and a PT-RS subcarrier offset of 10 for a resource offset parameter value of “10” for the first DMRS configuration type; and A PT-RS subcarrier offset of 0 for a resource offset parameter value of “11” for the first DMRS configuration type; The lines, A line associated with DMRS port 1009, said line being: a PT-RS subcarrier offset of 6 for a resource offset parameter value of “00” for the first DMRS configuration type; and a PT-RS subcarrier offset of 8 for a resource offset parameter value of “01” for the first DMRS configuration type; and a PT-RS subcarrier offset of 0 for a resource offset parameter value of “10” for the first DMRS configuration type; and A PT-RS subcarrier offset of 2 for a resource offset parameter value of “11” for the first DMRS configuration type; The lines, A row associated with a DMRS port 1010, said row comprising: a PT-RS subcarrier offset of 5 for a resource offset parameter value of “00” for the first DMRS configuration type; and a PT-RS subcarrier offset of 7 for a resource offset parameter value of “01” for the first DMRS configuration type; and a PT-RS subcarrier offset of 11 for a resource offset parameter value of “10” for the first DMRS configuration type; and A PT-RS subcarrier offset of 1 for a resource offset parameter value of “11” for the first DMRS configuration type; The lines, A line associated with DMRS port 1011, said line being: a PT-RS subcarrier offset of 7 for a resource offset parameter value of “00” for the first DMRS configuration type; and a PT-RS subcarrier offset of 9 for a resource offset parameter value of “01” for the first DMRS configuration type; and a PT-RS subcarrier offset of 1 for a resource offset parameter value of “10” for the first DMRS configuration type; and A PT-RS subcarrier offset of 3 for a resource offset parameter value of “11” for the first DMRS configuration type; The lines, A row associated with DMRS port 1012, said row comprising: a PT-RS subcarrier offset of 6 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 7 for a resource offset parameter value of “01” for the second DMRS configuration type; and a PT-RS subcarrier offset of 0 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 1 for a resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with DMRS port 1013, said row being: a PT-RS subcarrier offset of 7 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 0 for a resource offset parameter value of “01” for the second DMRS configuration type; and a PT-RS subcarrier offset of 1 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 6 for a resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with a DMRS port 1014, said row comprising: a PT-RS subcarrier offset of 8 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 9 for a resource offset parameter value of “01” for the second DMRS configuration type; and a PT-RS subcarrier offset of 2 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 3 for a resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with a DMRS port 1015, said row comprising: a PT-RS subcarrier offset of 9 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 2 for a resource offset parameter value of “01” for a second DMRS configuration type; and a PT-RS subcarrier offset of 3 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 8 for a resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with DMRS port 1016, said row comprising: a PT-RS subcarrier offset of 10 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 11 for a resource offset parameter value of “01” for the second DMRS configuration type; and a PT-RS subcarrier offset of 4 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 5 for a resource offset parameter value of “11” for the second DMRS configuration type; The lines, A line associated with DMRS port 1017, said line being: a PT-RS subcarrier offset of 11 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 4 for a resource offset parameter value of “01” for the second DMRS configuration type; and a PT-RS subcarrier offset of 5 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 10 for a resource offset parameter value of “11” for the second DMRS configuration type; Defines the line and Includes.

[0035] In one embodiment, the uplink table comprises: A row associated with DMRS port 1000, said row being: a PT-RS subcarrier offset of 0 for a resource offset parameter value of “00” for the first DMRS configuration type; and a PT-RS subcarrier offset of 2 for a resource offset parameter value of “01” for the first DMRS configuration type; and a PT-RS subcarrier offset of 6 for a resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 8 for a resource offset parameter value of “11” for the first DMRS configuration type; and a PT-RS subcarrier offset of 0 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 1 for a resource offset parameter value of “01” for a second DMRS configuration type; and a PT-RS subcarrier offset of 6 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 7 for a resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with DMRS port 1001, said row being: a PT-RS subcarrier offset of 2 for a resource offset parameter value of “00” for the first DMRS configuration type; and a PT-RS subcarrier offset of 4 for a resource offset parameter value of “01” for the first DMRS configuration type; and a PT-RS subcarrier offset of 8 for a resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 10 for a resource offset parameter value of “11” for the first DMRS configuration type; and a PT-RS subcarrier offset of 1 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 6 for a resource offset parameter value of “01” for the second DMRS configuration type; and a PT-RS subcarrier offset of 7 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 0 for a resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with DMRS port 1002, said row comprising: a PT-RS subcarrier offset of 1 for a resource offset parameter value of “00” for the first DMRS configuration type; and a PT-RS subcarrier offset of 3 for a resource offset parameter value of “01” for the first DMRS configuration type; and a PT-RS subcarrier offset of 7 for a resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 9 for a resource offset parameter value of “11” for the first DMRS configuration type; and a PT-RS subcarrier offset of 2 for a resource offset parameter value of “00” for a second DMRS configuration type; and a PT-RS subcarrier offset of 3 for a resource offset parameter value of “01” for the second DMRS configuration type; and a PT-RS subcarrier offset of 8 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 9 for a resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with DMRS port 1003, said row being: a PT-RS subcarrier offset of 3 for a resource offset parameter value of “00” for the first DMRS configuration type; and a PT-RS subcarrier offset of 5 for a resource offset parameter value of “01” for the first DMRS configuration type; and a PT-RS subcarrier offset of 9 for a resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 11 for a resource offset parameter value of “11” for the first DMRS configuration type; and a PT-RS subcarrier offset of 3 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 8 for a resource offset parameter value of “01” for the second DMRS configuration type; and a PT-RS subcarrier offset of 9 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 2 for a resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with DMRS port 1004, said row comprising: a PT-RS subcarrier offset of 4 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 5 for a resource offset parameter value of “01” for the second DMRS configuration type; and a PT-RS subcarrier offset of 10 for a resource offset parameter value of “10” for the second DMRS configuration type; and A PT-RS subcarrier offset of 11 for a resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with DMRS port 1005, said row being: a PT-RS subcarrier offset of 5 for a resource offset parameter value of “00” for the second DMRS configuration type; and a PT-RS subcarrier offset of 10 for a resource offset parameter value of “01” for the second DMRS configuration type; and a PT-RS subcarrier offset of 11 for a resource offset parameter value of “10” for a second DMRS configuration type; and A PT-RS subcarrier offset of 4 for a resource offset parameter value of “11” for the second DMRS configuration type; Defines the line and Further includes:

[0036] In one embodiment, the PT-RS port is mapped to one DMRS subcarrier of the associated DMRS port in each of one or more RBs assigned to the PT-RS port, and the one DMRS subcarrier to which the PT-RS port is mapped in each RB is defined as a function of the determined PT-RS subcarrier offset.

[0037] In one embodiment, the PT-RS subcarrier offset is with respect to the subcarrier with the lowest frequency in each of one or more RBs.

[0038] In one embodiment, N RB For a PDSCH or PUSCH scheduled with (≥ 1) RBs, RB Corresponding RBs TIFF2026500273000019.tif5170 subcarriers are arranged in order from 0 to TIFF2026500273000020.tif5170 are numbered in ascending order, and the PTRS port is N RB The subcarriers mapped in RBs are Given by TIFF2026500273000021.tif7170, · TIFF2026500273000022.tif7170 is the PT-RS subcarrier offset, i=0,1,2,... ·K PT-RS is the frequency density of PT-RS, and K PT-RS ∈{2,4}, · TIFF2026500273000023.tif7170 is the RB offset for PT-RS, Given by TIFF2026500273000024.tif13170, · TIFF2026500273000025.tif5170 is the number of subcarriers per RB, n RNTI is the RNTI associated with the DCI that schedules the transmission.

[0039] In one embodiment, a UE may be scheduled in the downlink such that the number of consecutively scheduled RBs for the UE is odd and only PT-RS subcarrier offsets within the range of 0 to 7, inclusive, are allowed. In one embodiment, an RB is scheduled for the downlink and the determined PT-RS subcarrier offset is outside the allowed range of 0 to 7, inclusive, and based thereon, the UE assumes that a PT-RS is not present in the RB. In another embodiment, an RB is scheduled for the downlink and the determined PT-RS subcarrier offset is outside the allowed range of 0 to 7, inclusive, and based thereon, the UE assumes that a PT-RS is not present in the RB with the lowest index among each set of consecutively scheduled RBs and assumes that a PT-RS is present in the remaining RBs. In another embodiment, an RB is scheduled for the downlink and the determined PT-RS subcarrier offset is outside the allowed range of 0 to 7, inclusive, and based thereon, the UE assumes that a PT-RS is not present in the RB if the RB is associated with an orphaned resource element. In another embodiment, an RB is scheduled for the downlink and the determined PT-RS subcarrier offset is outside the allowed range of 0 to 7, inclusive, and based thereon, the UE does not transmit PT-RS in the RB. In another embodiment, an RB is scheduled for the downlink and the determined PT-RS subcarrier offset is outside the allowed range of 0 to 7, inclusive, and based thereon, the UE does not transmit PT-RS in the RB with the highest index between each set of consecutively scheduled RBs and transmits PT-RS in the remaining RBs. In another embodiment, an RB is scheduled for the downlink and the determined PT-RS subcarrier offset is outside the allowed range of 0 to 7, inclusive, and based thereon, the UE does not transmit PT-RS in the RB with the lowest index between each set of consecutively scheduled RBs and transmits PT-RS in the remaining RBs.

[0040] Corresponding embodiments of a UE are also disclosed. In one embodiment, a UE for a wireless communication system is adapted to, for each RB of one or more RBs allocated for a PT-RS port configured for the UE, determine a PT-RS subcarrier offset for the PT-RS port from a table based on the DMRS port associated with the PT-RS port, a DMRS configuration type, and a resource element offset parameter configured for the UE. The DMRS port associated with the PT-RS port is one of a plurality of DMRS ports, eight of the plurality of DMRS ports being associated with a first DMRS configuration type and twelve of the plurality of DMRS ports being associated with a second DMRS configuration type. Each row of the table is associated with one of the plurality of DMRS ports and specifies different PT-RS subcarrier offsets for the PT-RS port associated with one of the plurality of DMRS ports for different resource element offset parameter values ​​for at least one of the first DMRS configuration type and the second DMRS configuration type. The UE is further adapted to, for each RB of one or more RBs assigned for the PT-RS port configured for the UE, transmit or receive a PT-RS on the PT-RS port in the RB according to the determined PT-RS subcarrier offset. In this manner, phase tracking with the PT-RS for a PDSCH or PUSCH having up to eight layers is enabled by assigning appropriate subcarrier offsets.

[0041] In one embodiment, a UE for a wireless communication system comprises a communication interface including a transmitter and a receiver, and processing circuitry associated with the communication interface. The processing circuitry is configured to cause the UE to, for each RB of one or more RBs assigned for a PT-RS port configured for the UE, determine a PT-RS subcarrier offset for the PT-RS port from a table based on the DMRS port associated with the PT-RS port, a DMRS configuration type, and a resource element offset parameter configured for the UE. The DMRS port associated with the PT-RS port is one of a plurality of DMRS ports, eight of the plurality of DMRS ports being associated with a first DMRS configuration type and twelve of the plurality of DMRS ports being associated with a second DMRS configuration type. Each row of the table is associated with one of the plurality of DMRS ports and specifies different PT-RS subcarrier offsets for the PT-RS port associated with one of the plurality of DMRS ports for different resource element offset parameter values ​​for at least one of the first DMRS configuration type and the second DMRS configuration type. The processing circuitry is further configured to cause the UE, for each RB of one or more RBs assigned for the PT-RS port configured for the UE, to transmit or receive a PT-RS on the PT-RS port in the RB according to the determined PT-RS subcarrier offset. In this manner, phase tracking with the PT-RS for a PDSCH or PUSCH having up to eight layers is enabled by assigning appropriate subcarrier offsets.

[0042] Also disclosed are embodiments of a method performed by a network node in a wireless communication system. In one embodiment, the method includes, for each RB of one or more RBs allocated for a PT-RS port configured for a UE, determining a PT-RS subcarrier offset for the PT-RS port from a table based on the DMRS port associated with the PT-RS port, a DMRS configuration type, and a resource element offset parameter configured for the UE. The DMRS port associated with the PT-RS port is one of a plurality of DMRS ports, eight of the plurality of DMRS ports being associated with a first DMRS configuration type and twelve of the plurality of DMRS ports being associated with a second DMRS configuration type. Each row of the table is associated with one of the plurality of DMRS ports and specifies different PT-RS subcarrier offsets for the PT-RS port associated with one of the plurality of DMRS ports for different resource element offset parameter values ​​for at least one of the first DMRS configuration type and the second DMRS configuration type. The method further includes, for each RB of one or more RBs assigned for the PT-RS port configured for the UE, transmitting or receiving a PT-RS on the PT-RS port in the RB according to the determined PT-RS subcarrier offset. In this manner, phase tracking with the PT-RS for a PDSCH or PUSCH having up to eight layers is enabled by assigning appropriate subcarrier offsets.

[0043] Also disclosed are embodiments of a method performed by a transmitting node in a wireless communication system. In one embodiment, the method performed by the transmitting node in the wireless communication system includes determining a PT-RS to PxSCH power ratio per spatial layer per resource element (RE) for scheduled physical downlink / uplink shared channel (PxSCH) transmissions for a UE, the PxSCH transmissions having up to eight spatial layers and on more than four antenna ports. The method further includes transmitting the scheduled PxSCH transmissions having up to eight layers and transmitting the PT-RS on the PT-RS port along with the PxSCH transmissions at a transmit power according to the determined PT-RS to PxSCH power ratio per spatial layer per RE.

[0044] In one embodiment, the PxSCH transmission is a physical downlink shared channel (PDSCH) transmission having seven or eight layers, the determined PT-RS to PxSCH power ratio per spatial layer per RE is a PT-RS to PDSCH power ratio per spatial layer per RE, and the transmitting node is a network node in a wireless communication system.

[0045] In one embodiment, determining the PT-RS to PDSCH power ratio per spatial layer per RE for the scheduled PDSCH transmission is based on a table that specifies multiple PT-RS to PDSCH power ratio values ​​per spatial layer per RE for a respective multiple number of PDSCH spatial layer values, where the multiple numbers of PDSCH spatial layer values ​​include 1, 2, 3, 4, 5, 6, 7, and 8. In one embodiment, each of the one or more rows of the table corresponds to a value of a downlink PT-RS configuration parameter “EPRE-ratio,” where “EPRE-ratio” is signaled from the network node to the UE and can have an integer value from 0 to 3.

[0046] In one embodiment, the table specifies a PT-RS to PDSCH power ratio value per spatial layer per RE of 8.45 for the case where the PDSCH transmission consists of 7 spatial layers, and a PT-RS to PDSCH power ratio value per spatial layer per RE of 9 for the case where the PDSCH transmission consists of 8 spatial layers. In one embodiment, the table further specifies a PT-RS to PDSCH power ratio value per spatial layer per RE of 0 when the PDSCH transmission consists of one spatial layer, a PT-RS to PDSCH power ratio value per spatial layer per RE of 3 when the PDSCH transmission consists of two spatial layers, a PT-RS to PDSCH power ratio value per spatial layer per RE of 4.77 when the PDSCH transmission consists of three spatial layers, a PT-RS to PDSCH power ratio value per spatial layer per RE of 6 when the PDSCH transmission consists of four spatial layers, a PT-RS to PDSCH power ratio value per spatial layer per RE of 7 when the PDSCH transmission consists of five spatial layers, and a PT-RS to PDSCH power ratio value per spatial layer per RE of 7.78 when the PDSCH transmission consists of six spatial layers.

[0047] In one embodiment, the value of the PT-RS to PDSCH power ratio per spatial layer per RE for n (n=7, 8) PDSCH spatial layers in one of the one or more rows is given by 10log10(n).

[0048] In one embodiment, determining the PT-RS to PDSCH power ratio per spatial layer per RE for a scheduled PDSCH transmission with seven or eight spatial layers includes determining a row in a table based on a configured parameter “EPRE-ratio” and determining a value of the PT-RS to PDSCH power ratio per spatial layer per RE in the determined row based on the number of spatial layers of the PDSCH.

[0049] In one embodiment, the PxSCH transmission is a PUSCH transmission having up to eight layers and on up to eight antenna ports at the UE, the determined PT-RS to PxSCH power ratio per spatial layer per RE is a PT-RS to PUSCH power ratio per spatial layer per RE, and the transmitting node is the UE.

[0050] In one embodiment, determining the PT-RS to PUSCH power ratio per spatial layer per RE for the scheduled PUSCH transmission is based on a table specifying multiple PT-RS to PUSCH power ratio values ​​per spatial layer per RE for a respective multiple number of PUSCH spatial layer values, wherein the multiple numbers of PDSCH spatial layer values ​​include 1, 2, 3, 4, 5, 6, 7, and 8. In one embodiment, each of the one or more rows of the table corresponds to a value of an uplink configuration parameter "UL-PTRS-power" received by the UE from a network node. In one embodiment, for fully coherent PUSCH transmission on up to eight antenna ports, each of the multiple PT-RS to PUSCH power ratio values ​​per spatial layer per RE in at least one of the one or more rows in the table is calculated based on a respective number of PUSCH spatial layers associated with the PT-RS port, as defined by: TIFF2026500273000026.tif7170 where, TIFF2026500273000027.tif6170 is the PT-RS to PUSCH power ratio per spatial layer per RE, TIFF2026500273000028.tif7170 is the number of spatial layers in the PUSCH transmission. In one embodiment, for non-coherent PUSCH transmission on up to eight antenna ports, each spatial layer of the PUSCH transmission is transmitted on only one of the up to eight antenna ports, and each of the multiple PT-RS to PUSCH power ratio values ​​per spatial layer per RE in at least one of the one or more rows in the table is calculated based on the number of PT-RS ports scheduled for the PUSCH, as defined by: TIFF2026500273000029.tif6170 where, TIFF2026500273000030.tif6170 is the PT-RS to PUSCH power ratio per spatial layer per RE, and Q p is the number of PT-RS ports scheduled for PUSCH transmission. In one embodiment, for partially coherent PUSCH transmission on up to eight antenna ports, the up to eight antenna ports of the UE are divided into two or more antenna port groups, the PUSCH transmission in each of the groups is coherent, and each of the multiple PT-RS to PUSCH power ratio values ​​per spatial layer per RE in at least one of the one or more rows in the table is calculated based on the respective number of PUSCH spatial layers in the same antenna group as the PT-RS, as defined by: TIFF2026500273000031.tif7170 where, TIFF2026500273000032.tif6170 is the PT-RS to PUSCH power ratio per spatial layer per RE, TIFF2026500273000033.tif7170 is the number of spatial layers of PUSCH transmissions transmitted in the same antenna port group as the PT-RS, and Q p is the number of PT-RS ports scheduled for PUSCH transmission.

[0051] In one embodiment, determining the PT-RS to PUSCH power ratio per spatial layer per RE for the scheduled PUSCH transmission includes determining a row in the table based on the configured parameter “UL-PTRS-power” and whether the PUSCH transmission is fully coherent, non-coherent, or partially coherent, and determining a value of the PT-RS to PUSCH power ratio per spatial layer per RE based on the respective number of spatial layers of the PUSCH transmission on the antenna port associated with the PT-RS port.

[0052] Corresponding embodiments of a transmitting node for a wireless communication system are also disclosed. In one embodiment, a transmitting node for a wireless communication system is adapted to determine a PT-RS to PxSCH power ratio per spatial layer per RE for a scheduled PxSCH transmission for a UE, the PxSCH transmission having up to eight spatial layers and on more than four antenna ports. The transmitting node is further adapted to transmit the scheduled PxSCH transmission having up to eight layers and to transmit, along with the PxSCH transmission, a PT-RS on the PT-RS port at a transmit power according to the determined PT-RS to PxSCH power ratio per spatial layer per RE.

[0053] In one embodiment, a transmitting node for a wireless communication system comprises a processing circuit, the processing circuit configured to cause the transmitting node to determine a PT-RS to PxSCH power ratio per spatial layer per RE for a scheduled PxSCH transmission for a UE, the PxSCH transmission having up to eight spatial layers and on more than four antenna ports. The processing circuit is further configured to cause the transmitting node to transmit the scheduled PxSCH transmission having up to eight layers and to transmit, along with the PxSCH transmission, a PT-RS on the PT-RS port at a transmit power according to the determined PT-RS to PxSCH power ratio per spatial layer per RE.

[0054] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate several aspects of the present disclosure and, together with the description, serve to explain the principles of the disclosure. [Brief explanation of the drawings]

[0055] [Figure 1A] FIG. 1 is a diagram illustrating an example of a New Radio (NR) slot. [Figure 1B] FIG. 1 is a diagram illustrating an example of a resource block (RB) in NR. [Figure 1C] FIG. 1 illustrates a phase tracking reference signal (PT-RS) downlink configuration information element and a PT-RS uplink configuration information element as defined in 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 38.331 v17.2.0. [Figure 1D] FIG. 1D shows an example of a PT-RS resource element (RE) in a PT-RS RB for ½ time domain density, where the PT-RS port is associated with Type 1 Demodulation Reference Signal (DMRS) port 1, the radio resource control (RRC) parameter resourceElementOffset is set as “offset10”, and with single-symbol DMRS in the RB (left side of FIG. 1D ) and double-symbol DMRS in the RB (right side of FIG. 1D ). [Figure 1E] FIG. 1E shows an example in which a PT-RS port is associated with a single symbol type 1 DMRS port 1 (shown on the left side of FIG. 1E) and a single symbol type 2 DMRS port 1 (shown on the right side of FIG. 1E), both again with the RRC parameter resourceElementOffset set as “offset10”, but with a PTRS time density of L=1. [Figure 2A] 1 illustrates the relationship between DMRS ports and code division multiplexing (CDM) groups for a physical uplink shared channel (PUSH) for Type 1 DMRS. [Figure 2B] FIG. 10 is a diagram showing the relationship between DMRS ports and CDM groups for PUSH for Type 2 DMRS. [Figure 2C] 10 shows a case where the number of DMRS ports per CDM group is doubled for Type 1 DMRS. [Figure 2D] FIG. 10 illustrates the case where the number of DMRS ports per CDM group is doubled for Type 2 DMRS. [Figure 2E]FIG. 10 illustrates an example of a table specifying downlink PT-RS subcarrier offsets for an increased number of DMRS ports for Type 1 DMRS and Type 2 DMRS, in accordance with one embodiment of the present disclosure. [Figure 2F] FIG. 10 illustrates an example of a table specifying uplink PT-RS subcarrier offsets for an increased number of DMRS ports for Type 1 DMRS and Type 2 DMRS, in accordance with one embodiment of the present disclosure. [Figure 3A] “offset01” and DMRS antenna port according to one exemplary embodiment of the present disclosure.

number

number

[0056] The embodiments described below represent information to enable those skilled in the art to practice the embodiments and illustrate the best modes of practicing the embodiments. Upon reading the following description in light of the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure and will recognize applications of these concepts not specifically addressed herein. It is understood that these concepts and applications fall within the scope of the present disclosure.

[0057] Several challenges exist. In existing New Radio (NR) releases up to Release 17, a phase tracking reference signal (PT-RS or PTRS) can be configured with up to four layers of physical downlink shared channels (PDSCHs) for Type-1 demodulation reference signals (DMRSs) and up to six layers for Type-2 DMRS, as well as up to four layers of physical uplink shared channels (PUSCHs). With the increased number of DMRS ports in NR Rel-18, a question arises as to how to allocate PT-RS subcarriers when a PT-RS port is associated with one of the new DMRS ports in NR Rel-18. Another question is how to allocate the PT-RS-to-PDSCH or PUSCH power ratio per resource element (RE) per layer when a PT-RS can be associated with a PDSCH with more than six layers or DMRS ports, or with a PUSCH with up to eight layers transmitted on up to eight antenna ports.

[0058] Some aspects of the present disclosure and their embodiments may provide solutions to these or other problems. Some embodiments of the present disclosure provide a method for assigning subcarrier offsets for PT-RS ports associated with a new NR Rel-18 DMRS port, in which existing rows in Table 7.4.1.2.2-1 of 3GPP TS38.211 for the downlink (DL) (reproduced herein as Table 1) and in Table 6.4.1.2.2.1-1 of 3GPP TS38.211 for the uplink (UL) (reproduced herein as Table 2) are reused for Rel-18 DMRS ports with the same port index, and new rows are added for the remainder of the Rel-18 DMRS ports. For a given value of the radio resource control (RRC) parameter "resourceElementOffset," different subcarrier offsets are assigned to the PT-RS associated with different DMRS ports.

[0059] Some embodiments of the present disclosure provide methods for allocating a per-layer PT-RS-to-PDSCH power ratio per RE for PDSCHs with seven and eight layers, and for allocating a per-layer PT-RS-to-PUSCH power ratio per RE for PUSCHs with more than four transmit (Tx) antenna ports and up to eight layers.

[0060] According to some embodiments of the present disclosure, when both a PT-RS port and a Rel-18 DMRS port are configured for a UE, the PT-RS port may be associated with one of eight Type 1 DMRS ports or twelve Type 2 DMRS ports.

[0061] According to some embodiments of the present disclosure, a method for assigning a subcarrier offset for a PT-RS port in each resource block (RB) assigned for the PT-RS port is provided, the method including: defining a table for DL ​​(e.g., FIG. 2E) and a table for UL (e.g., FIG. 2F), where each row is associated with a DMRS port to which a PT-RS is associated; For a given associated DMRS port of either Type 1 or Type 2, and higher layer configuration of the "resourceElementOffset" value, the PT-RS subcarrier offset may be determined from one of the above tables. UE Capability: Supports PTRS for orphan RBs in case of Type 1 DMRS (e.g., Figure 3A)

[0062] According to some embodiments of the present disclosure, when both a PT-RS port and a Rel-18 DMRS port are configured for a UE, a PDSCH or PUSCH is scheduled with up to eight layers.

[0063] According to some embodiments of the present disclosure, there is provided a method for determining a PT-RS to PDSCH or PUSCH power ratio per layer per RE, the method including: Specifying the PT-RS to PDSCH power ratio per layer per RE for PDSCH scheduled with 7 and 8 layers according to the table shown in Figure 4A-1. For partially coherent codebooks, the PT-RS to PUSCH power ratio per layer per RE may be PT-RS port specific or common to all PT-RS ports. o In the PT-RS port specific case, for each PT-RS port, the above ratio is determined by both the number of scheduled PUSCH layers associated with the PT-RS port and the total number of scheduled PT-RS ports associated with PUSCHs (see Figure 4C-1). In the case of a common PT-RS port, the above ratio for a given number of scheduled PUSCH layers may be determined based on a predefined table for a given number of antenna port groups and / or a given number of scheduled PT-RS ports (see Figures 4C-2, 4C-4, and 4C-5). For a fully coherent codebook, the PT-RS to PUSCH power ratio per layer per RE is determined by the number of scheduled PUSCH layers (see Figure 4A-2). For non-coherent codebooks, the PT-RS to PUSCH power ratio per layer per RE is determined by the number of scheduled PTs (see Figure 4A-4).

[0064] According to some embodiments of the present disclosure, communication systems and devices adapted to perform one or a combination of these steps are also provided.

[0065] Some embodiments may provide one or more of the following technical advantage(s): The method enables phase tracking with PT-RS for PDSCH or PUSCH with up to eight layers by assigning appropriate subcarrier offsets and PT-RS to PDSCH or PUSCH power ratios in those scenarios.

[0066] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings, in which the embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0067] When the number of DMRS ports is increased by applying a length-4 frequency-domain orthogonal cover code (FD-OCC) code in each of the legacy Rel-15 DMRS code division multiplexing (CDM) groups and the DMRS ports are configured according to Figures 2C and 2D, in the uplink (UL), the eight associated single-symbol Type 1 DMRS ports are ports {0, 1, 2, 3, 8, 9, 10, 11}, and the twelve associated single-symbol Type 2 DMRS ports are ports {0, 1, 2, 3, 4, 5, 12, 13, 14, 15, 16, 17}. Similarly, the associated single-symbol Type 1 DMRS ports in the downlink (DL) are Port 1000 + {0,1,2,3,8,9,10,11}, and the associated Type 2 DMRS ports are Port 1000 + {0,1,2,3,4,5,12,13,14,15,16,17}. These DMRS port indices are used as an example in the following description. Other ways of indexing the DMRS ports are also possible.

[0068] PT-RS subcarrier offset It is assumed that a UL PT-RS port may be associated with one of eight Type 1 DMRS ports {0,1,2,3,8,9,10,11} for the PUSCH, and a DL PT-RS port may be associated with one of eight Type 1 DMRS ports 1000+{0,1,2,3,8,9,10,11} for the PDSCH.

[0069] In one embodiment, an UL PT-RS port may be associated with one of 12 Type-2 DMRS ports {0,1,2,3,4,5,12,13,14,15,16,17} for the PUSCH, and a DL PT-RS port may be associated with one of 12 Type-2 DMRS ports 1000+{0,1,2,3,4,5,12,13,14,15,16,17} for the PDSCH.

[0070] In one embodiment, the subcarrier offset for the PT-RS associated with the DMRS port is TIFF2026500273000036.tif7170 can be assigned as shown in FIG. 2E for DL ​​PT-RS and as shown in FIG. 2F for UL PT-RS, where the rows with p=1000 to p=1005 in FIG. 2E, and TIFF2026500273000037.tif5170~ For rows with TIFF2026500273000038.tif5170, the legacy tables (i.e., Table 7.4.1.2.2-1 in 3GPP TS38.211 for DL ​​and Table 6.4.1.2.2.1-1 in 3GPP TS38.211 for UL) are reused. In another embodiment, a subset of the columns may be included in the specification. For example, only offset=00 may be included for Type 2 DMRS.

[0071] In one embodiment, in NR for Rel-18 DMRS, new PTRS subcarrier offset tables (one for DL ​​and / or one for UL) are introduced, where some of the legacy entries (i.e., the rows for ports 1000-1005 in FIG. 2E and the rows for ports 0-5 in FIG. 2F) are also updated, i.e., some of the entries for DMRS antenna ports 1000-1005 (FIG. 2E) or 0-5 (FIG. 2F) in the tables shown in FIG. 2E and FIG. 2F may be changed with respect to the values ​​shown in FIG. 2E and FIG. 2F.

[0072] The allocations in Figures 2E and 2F ensure that for the same resourceElementOffset setting, i.e., one of the four settings, offset00, offset01, offset10, and offset11, PT-RS ports associated with different DMRS ports are allocated in different subcarriers. This will prevent collisions of PT-RS ports scheduled in the same RB. For example, when eight UEs are co-scheduled in the same RB for MU-MIMO and a single layer is scheduled for each UE, different DMRS ports will be scheduled for different UEs. For Type-1 DMRS, all eight DMRS ports (i.e., ports 1000-1003 and 1008-10011 for PDSCH and ports 0-3 and 8-11 for PUSCH) will be allocated. If the PT-RS is configured identically for all UEs and all PT-RS ports happen to be assigned in the same RB, the PT-RS ports cannot overlap and must be assigned in different REs (i.e., with different subcarrier offsets). In the case of the subcarrier offset assignment in Figures 2E and 2F, the PT-RSs associated with different DMRS ports are always assigned to different subcarriers.

[0073] Orphan RB for Type 1 DMRS:

[0074] When Rel-18 DM-RS extended configuration type 1 is configured, the number of REs per CDM group on the scheduled bandwidth may not be an integer multiple of the FD-OCC code length (i.e., there are 6 REs per CDM group per RB for configuration type 1, and the FD-OCC code length is 4). This is called an "orphan RE." For example, this occurs when an odd number of consecutive RBs are scheduled or when an odd number of PRBs offset from point A (CRB0) of the scheduled PDSCH is scheduled. One possible solution is to apply a scheduling restriction such that the number of consecutively scheduled PRBs and the PRB offset from CRB0 of the scheduled PDSCH are even. However, in Rel-18, there is a UE capability when such scheduling restriction does not need to be applied. That is, when the UE indicates this capability, the UE can be scheduled such that the number of consecutively scheduled PRBs is odd. However, how to implement DMRS channel estimation in this case is up to the UE implementation. In one embodiment, for downlink PT-RS, when the UE indicates this capability and the UE can be scheduled with an odd number of consecutive PRBs, only subcarrier offsets in the range 0 to 7 are allowed. This means that the following combinations are allowed, with reference to Figures 2E and 2F: For offset00, in FIG. 2E, all combinations of ports 1000 to 1003 and 1008 to 1011 are allowed. For offset01, in FIG. 2E, the combinations of ports 1000 to 1003, 1008, and 1010 are allowed. For offset10, in FIG. 2E, the combination of ports 1000, 1002, 1009, and 1011 is allowed. For offset11, in FIG. 2E, combinations of ports 1008 to 1011 are allowed. For offset00, in FIG. 2F, all combinations with ports 0 to 3 and 8 to 11 are allowed. For offset01, in FIG. 2F, combinations of ports 0 to 3, 8, and 10 are allowed. For offset 10, in FIG. 2F, combinations with ports 0, 2, 9, and 11 are allowed. Regarding offset 11, in FIG. 2F, a combination of ports 8 to 11 is allowed.

[0075] In one embodiment, in the downlink, when the number of consecutively scheduled PRBs is odd or the PRB offset of the scheduled PDSCH from CRB0 is odd, and when an impermissible combination (i.e., a combination not listed above) is signaled to the UE, the UE assumes that the PT-RS is not present in one or more PRBs. In one variant of the embodiment, when an impermissible combination is signaled to the UE, the UE assumes that the PT-RS is not present in the last PRB (e.g., the PRB with the highest PRB index) between each set of consecutively scheduled PRBs and assumes that the PT-RS is present in the remaining PRBs. In another variant of the embodiment, when an impermissible combination is signaled to the UE, the UE assumes that the PT-RS is not present in the first PRB (e.g., the PRB with the lowest PRB index) between each set of consecutively scheduled PRBs and assumes that the PT-RS is present in the remaining PRBs. In yet another variant of the embodiment, the UE assumes that the PT-RS is not present in an RB associated with an orphan RE.

[0076] In another embodiment, in the uplink, when the number of consecutively scheduled PRBs or the PRB offset of the scheduled PUSCH from CRB0 is odd and when an impermissible combination (i.e., a combination not listed above) is signaled to the UE, the UE does not transmit PT-RS in one or more PRBs. In one variation of this embodiment, when an impermissible combination is signaled to the UE, the UE does not transmit PT-RS in the last PRB (e.g., the PRB with the highest PRB index) between each set of consecutively scheduled PRBs and transmits PT-RS in the remaining PRBs. In another variation of the embodiment, when an impermissible combination is signaled to the UE, the UE does not transmit PT-RS in the first PRB (e.g., the PRB with the lowest PRB index) between each set of consecutively scheduled PRBs and transmits PT-RS in the remaining PRBs.

[0077] Figure 3A shows the offset01 and DMRS antenna ports. TIFF2026500273000039.tif5170, where the subcarrier offset is Here is an example, TIFF2026500273000040.tif7170.

[0078] In one embodiment, the parameter "resourceElementOffset" defined in the PTRS-DownlinkConfig and PTRS-UplinkConfig information elements in 3GPP TS38.331 used for Rel-15 DMRS is also reused for Rel-18 enhanced DMRS. One benefit with this solution is that the amount of radio resource control (RRC) signaling is reduced compared to introducing a new dedicated parameter for Rel-18 DMRS PTRS offset assignment when a UE is configured with both Rel-15 and Rel-18 DMRS.

[0079] In one embodiment, as shown in Figures 3B and 3C, a new dedicated parameter, herein referred to as "resourceElementOffset-Rel18", is introduced in the PTRS-DownlinkConfig information element and / or the PTRS-UplinkConfig information element in 3GPP TS38.331. One benefit with this solution is that different PTRS mappings can be used for Rel-15 and Rel-18 DMRS (e.g., offset 00 is used for Rel-15 DMRS and offset 10 is used for Rel-18 DMRS), which can be useful, for example, if dynamic switching between Rel-15 and Rel-18 DMRS is supported because the NR base station (gNB) can then dynamically update the PTRS frequency allocation by switching between Rel-15 and Rel-18 DMRS (this can be useful, for example, if the network notices poor performance of the PTRS in the UL, which may be due to a conflicting PTRS from another UE in the same or a different cell, in which case the network can test switching the PTRS allocation by switching from Rel-15 DMRS to Rel-18 DMRS or vice versa). In some embodiments, the frequency density of the PTRS may be different for Rel-15 and Rel-18 DMRS configurations. In one embodiment, a different frequency density is configured for Rel-18 DMRS compared to the frequency density configured for Rel-15 DMRS. The newly configured frequency density may be referred to as "frequencyDensity-r18," and this new field may be introduced in the PTRS-DownlinkConfig and / or PTRS-UplinkConfig information elements in TS38.331.This is beneficial if dynamic switching between Rel-15 and Rel-18 DMRS is supported, where the gNB can then dynamically update the PTRS frequency density by switching between Rel-15 and Rel-18 DMRS.

[0080] In some other embodiments, the time density of the PTRS may be different for Rel-15 and Rel-18 DMRS configurations. In one embodiment, a different time density is configured for Rel-18 DMRS compared to the time density configured for Rel-15 DMRS. The newly configured time density may be referred to as "timeDensity-r18," and this new field may be introduced in the PTRS-DownlinkConfig and / or PTRS-UplinkConfig information elements in TS38.331. This is beneficial when dynamic switching between Rel-15 and Rel-18 DMRS is supported, where the gNB can then dynamically update the PTRS time density by switching between Rel-15 and Rel-18 DMRS.

[0081] PT-RS Power Boosting In NR Releases 15-17, the maximum number of PDSCH layers supported when a PT-RS is configured is four for Type-1 DMRS and six for Type-2 DMRS. The maximum number of PUSCH layers is four. In one embodiment, for a new Rel-18 DMRS port, up to eight layers may be supported for PDSCH or PUSCH when a PT-RS is configured. The transmit power of a PT-RS port may be boosted relative to the corresponding PDSCH or PUSCH transmit power per RE per layer according to the number of layers of the PDSCH or PUSCH associated with the PT-RS port.

[0082] In one embodiment, the PT-RS to PDSCH transmit power ratio ρ PTRSis given in FIG. 4A-1, where for layers 1 through 6, the legacy ratio may be reused, but for layers 7 and 8, the associated PT-RS port may be boosted by 8.45 dB (i.e., 10 log 10(7)) and 9.03 dB (i.e., 10 log 10(8); note that 9.03 may be truncated to 9 in the specification), respectively. Note that epre-Ratio values ​​other than epre-Ratio=0 as shown in the table in FIG. 4A-1 may be used to indicate 7 and 8 layers.

[0083] For PUSCH transmission with up to eight layers with up to eight Tx antenna ports, the Tx antenna ports may be fully coherent, partially coherent, or non-coherent. Corresponding fully coherent, partially coherent, or non-coherent codebooks may be designed accordingly. Each PUSCH layer is associated with a DMRS port. A PT-RS port may be associated with one or more of the PUSCH layers or DMRS ports.

[0084] In the case of a fully coherent codebook, the PUSCH layer is coded by a precoder w=[w(1),...,w(N Tx )] T ,w(i)≠0,i=1,...,N Tx , where N Tx is the number of Tx antennas. Multiple layers share the total transmit power across all antenna ports. For 7170 scheduled PUSCH layers, each PUSCH layer contributes 1 / 2 of the total transmit power. TIFF2026500273000042.tif7170, i.e. TIFF2026500273000043.tif7170. When a PT-RS is configured, it is associated with one of the DMRS ports and is precoded in the same manner as the associated DMRS port (or associated PUSCH layer). The PT-RS to PUSCH power ratio per layer per RE is 4A-2, where "xx" denotes the codepoint in the upper layer parameter "UL-PTRS-power" that indicates the row in the table. When codepoint "xx" is configured for "UL-PTRS-power," the UE determines the PT-RS transmit power according to the table shown in FIG. 4A-2.

[0085] In the case of a non-coherent codebook, each PUSCH layer is transmitted on only one of the antenna ports. The same applies to the PT-RS ports. For each PT-RS antenna port, the REs allocated to other PT-RS ports are unused (i.e., nothing is transmitted from the antenna port), and therefore the power normally allocated to those REs can be used for the PT-RS port to boost its transmit power. An example is shown in FIG. 4A-3, where two PT-RS ports are scheduled and 3 dB power boosting can be achieved for each of those PT-RS ports. Thus, in the case of a non-coherent codebook, the PT-RS-to-PUSCH power ratio per layer per RE is simply determined by the number of PT-RS ports associated with the PUSCH, i.e., TIFF2026500273000045.tif7170. In this case, the PT-RS to PUSCH power ratio per layer per RE is the same for all PT-RS ports. This is shown in Figure 4A-4.

[0086] For partially coherent codebooks, N Tx The antenna ports may be divided into multiple antenna port groups, where the antenna ports within each port group are coherent and the antenna ports in different antenna port groups are non-coherent. Each port group may be associated with a PT-RS port. Tx An example of w = 8 and two antenna port groups is shown in Figure 4B-1, where antenna ports 1-4 form a first port group and antenna ports 5-8 form a second port group. In one embodiment, each PUSCH layer is transmitted on all antenna ports in one of the two antenna port groups. When a PUSCH layer is transmitted in port group 1, the precoder is set to w = [w(1),...,w(4),0,...,0]. T where w(i)≠0 for i=1,...,4 and w(i)=0 for i=5,...,8. Similarly, when the PUSCH layer is transmitted in port group 2, the corresponding precoder is w=[0,...,0,w(5),w(6),w(7),w(8)]. T where w(i)=0 for i=1,...,4 and w(i)≠0 for i=5,...,8. In each antenna port group, up to four PUSH layers may be transmitted, with each layer being allocated 1 / r of the total transmit power available in the antenna port group, i.e., TIFF2026500273000046.tif8170, where r is the number of layers in the port group. It is assumed that the available power in each port group is 1 / 2 of the total transmit power on all antennas. Each port group is associated with a PT-RS port, and a maximum of two PT-RS ports are required.

[0087] The above can be extended to four antenna groups, and an example is shown in Figure 4B-2. In this case, the PUSCH layer is transmitted on all antenna ports in one of the four antenna port groups. For example, when the PUSCH layer is transmitted in port group 1, the precoder is set to w = [w(1),...,w(2),0,...,0]. T where w(i)≠0 for i=1,2 and w(i)=0 for i=3,...,8. Similarly, when the PUSCH layer is transmitted in port group 2, the corresponding precoder is w=[0,0,w(3),w(4),0,...,0)]. T where w(i)=0 for i=1,2,5,6,7,8 and w(i)≠0 for i=3,4. In each antenna port group, up to two PUSH layers may be scheduled or transmitted, and each layer is allocated 1 / r of the total transmit power in the antenna port group, i.e., TIFF2026500273000047.tif8170, where r is the number of layers scheduled in the port group. It is assumed that the available power in each port group is 1 / 4 of the total transmit power on all antennas. Each port group is associated with a PT-RS port, and a maximum of four PT-RS ports are required.

[0088] PT-RS Port-Specific PT-RS Power Boosting:

[0089] In one embodiment, for each PT-RS port, the PT-RS to PUSCH transmit power ratio per layer per RE is determined by the associated number of scheduled PUSCH layers in the same port group, i.e., TIFF2026500273000048.tif7170, where TIFF2026500273000049.tif7170 is the PTRS port k (k=0,1,...,Q pis the number of scheduled PUSCH layers in the antenna port group associated with Q p is the total number of scheduled PT-RS ports across the antenna port groups. For different PT-RS ports, depending on whether the same number of PUSCH layers or different numbers of PUSCH layers are scheduled in the corresponding antenna port groups, TIFF2026500273000050.tif6170 can be the same or different. For example, in the previous example with eight antenna ports, assume that PT-RS port 0 is associated with antenna port group 1 and PT-RS port 1 is associated with antenna port group 2. If two layers are scheduled in port group 1 and three layers are scheduled in port group 2, then Q p = 2 and PT-RS port 0, TIFF2026500273000051.tif6170 and PT-RS port 1, In another example with four antenna port groups, assume that PT-RS ports {0,1,2,3} are associated with antenna port groups {1,2,3,4}. If two layers are scheduled in port group 1 and one layer is scheduled in each of port groups {2,,3,4}, then Q p = 4 and PT-RS port 0, If the file is TIFF2026500273000053.tif6170 and the PT-RS port is {1,2,3}, The file is TIFF2026500273000054.tif6170.

[0090] Generally speaking, N ant,groups antenna groups and Q associated with the scheduled PUSCH p (Q p ≦N ant,groups) PT-RS ports, the PT-RS to PDSCH transmit power ratio per layer per RE for the PT-RS port is determined by the number of scheduled PUSCH layers associated with the PT-RS port in the same antenna port group, i.e., TIFF2026500273000055.tif7170. This is shown in Figure 4C-1. For eight Tx antennas with four port groups, each with two antenna ports, Please note that the file name is TIFF2026500273000056.tif7170.

[0091] Another case of mixed partially coherent and non-coherent port groups is possible, where in a first port group(s), the PUSCH layer is transmitted on only a single antenna port, while in a second port group(s), the PUSCH layer is transmitted on all antenna ports of a port group. In one embodiment, for the PT-RS ports associated with the first port group(s), the PT-RS-to-PUSCH transmit power ratio per layer per RE is determined according to FIG. 4A-4, while for the PT-RS ports associated with the second port group(s), the PT-RS-to-PUSCH transmit power ratio per layer per RE is determined according to FIG. 4A-2. For example, for eight antenna ports with four antenna port groups, five PUSCH layers are scheduled, as shown in FIG. 4C-2, where layers 1 and 2 are scheduled in antenna group 1 and layers 3-5 are scheduled in antenna groups 2-4 with one layer per group. w1 = [w1(1),0,, ...,0] T w2=[0 w2(2),0, ...,0] T In this case, for PT-RS port 0, the PT-RS to PUSCH transmit power ratio of PT-RS port 0 per layer per RE is, i.e., For PT-RS ports 1 to 3, the PT-RS to PUSCH transmit power ratios for PT-RS ports 1 to 3 per layer per RE are determined according to Figure 4A-2, i.e., TIFF2026500273000058.tif7170, k=1,2,3...

[0092] The PT-RS-to-PUSCH transmit power ratio per layer per RE for the PT-RS port described above represents the maximum PT-RS-to-PUSCH transmit power ratio per layer per RE that can be achieved. In some scenarios, the PT-RS-to-PUSCH transmit power ratio per layer per RE may be capped at a value Y (dB). For example, the maximum PT-RS-to-PUSCH transmit power ratio per layer may be limited to Y=6 dB. In that case, if the PT-RS-to-PUSCH transmit power ratio in Figures 4A-1, 4A-2, 4A-4, and 4C-1 is greater than Y, the PUSCH transmit power ratio will be set to Y dB. Alternatively, different rows in the tables in 4A-1, 4A-2, 4A-4, and 4C-1 may be used for that purpose. An example is shown in Figure 4C-3, where a new row "yy" is used.

[0093] Common PT-RS power boosting:

[0094] In some scenarios, it may be necessary to have the same power boosting for all PT-RS ports. In the following embodiments, it is assumed that the same PT-RS to PUSCH EPRE power ratio per RE per layer is determined for all scheduled PT-RS ports.

[0095] In one embodiment, different entries (and / or tables) for PT-RS to PUSCH EPRE power ratios are used for two antenna groups and four antenna groups for the partially coherent codebook.

[0096] In one embodiment, different entries (and / or tables) for the PT-RS to PUSCH EPRE power ratio are used depending on the number of scheduled PT-RS ports for the UE.

[0097] FIG. 4C-4 is an example of a PT-RS to PUSCH EPRE power ratio table for two antenna groups, where the maximum number of PTRS ports is equal to 2, i.e., Q p ∈{1,2}. When all PUSCH layers are scheduled in one antenna group, Q p When Q = 1 and some PUSCH layers are transmitted in one antenna group but other layers are transmitted in other antenna groups, Q p = 2. For up to five PUSCH layers, there is a possibility that one layer is scheduled / transmitted in the first antenna group, while the rest of the layers are scheduled / transmitted in the second antenna group. For a PT-RS in the first antenna group, if the PT-RS does not borrow power from unused / blanked out REs associated with the PT-RS port in the second antenna group, it will have the same power per RE per layer as the PUSCH in the same antenna group. When power is borrowed from unused / blanked out REs associated with the PT-RS port in the second antenna group, the PT-RS to PUSCH EPRE power ratio is 3 dB or (3Q p -3). For a PUSCH with six layers, at least two PUSCH layers need to be scheduled / transmitted in each of the two antenna groups. The PT-RS to PUSCH EPRE power ratio is at least 3 dB in the absence of power borrowing from unused / blanked REs associated with PT-RS ports in other antenna groups. In the presence of power borrowing, the PT-RS to PUSCH EPRE power ratio is at least 6 dB or 3 dB. pFor seven and eight PUSCH layers, at least three and four PUSCH layers need to be scheduled / transmitted in each of the two antenna groups, respectively. With power borrowing, the PT-RS to PUSCH EPRE power ratio is at least 7.78 dB (i.e., 10 log 10(6)) for seven layers and 9.03 dB (i.e., 10 log 10(8)) for eight layers. In the row with "UL-PTRS-power=00", it limits the maximum PT-RS power boosting to 6 dB.

[0098] To save PMI overhead, it may happen that not all possible rank combinations are allowed for an 8TX UE with two antenna groups. For example, the difference between the number of layers in one antenna group and the number of layers in the other antenna group may not be equal to or greater than 2. In this case, one or more of the rank combinations, i.e., 4+1 (i.e., 4 layers for the first antenna group and 1 layer for the second antenna group), 3+1, etc., will not be supported, and the PT-RS to PUSCH EPRE power ratio will be determined by the PT-RS port associated with the antenna group with the fewer assigned PUSCH layers, i.e., For example, for a total of three PUSCH layers, if one layer is in antenna group 1 and two layers are in antenna group 2, the PT-RS to PUSCH EPRE power ratio will be determined by the PT-RS port associated with antenna group 1, i.e., TIFF2026500273000060.tif7170. In this manner, the PT-RS to PUSCH EPRE power ratio for different numbers of PUSCh layers can also be determined. An example is shown in Figure 4C-3 in the row with "UL PTRS-power=01".

[0099] FIG. 4C-5 shows an example of how one or more entries of a PT-RS to PUSCH EPRE power ratio table for an 8TX UE with four antenna groups, where the maximum number of PTRS ports is equal to two, i.e., Q_p∈{1,2}, and each PT-RS port is associated with two antenna groups.

[0100] In one embodiment, for a UE supporting up to 4 PTRS and 8TX with four antenna groups, different PT-RS to PUSCH EPRE power ratio tables are used for different numbers of scheduled PTRS ports. An example of three such tables, for two, three, and four scheduled PTRS ports, respectively, is shown in Figure 4C-6.

[0101] Note that numbers in all tables are approximate and may be rounded down or up in specification. Note that only one or a subset of all rows and / or columns in each table may be specified (and other entries may be included in the remaining rows / columns of the table).

[0102] 5A illustrates a method performed in a wireless communication system for assigning subcarrier offsets for a phase tracking reference signal (PT-RS) port in each resource block (RB) allocated for the PT-RS port, where the PT-RS port is associated with one of eight Type 1 DMRS ports or one of twelve Type 2 DMRS ports when both the PT-RS port and a Rel18 DMRS port are configured for a user equipment (UE). The method includes one or more of (step 500A) determining a PT-RS subcarrier offset from either an uplink UL table or a downlink DL table for a given associated DMRS port and higher layer configuration of resource offset parameters, where each table row is associated with the DMRS port with which the PT-RS is associated; and (step 502-A) supporting the PTRS for orphan RBs in the case of Type 1 DMRS by the user equipment. The steps may be performed in any combination and in any order.

[0103] 5B is a flowchart illustrating a UE or network node (e.g., a base station such as a gNB) operation for PT-RS subcarrier offset allocation for each RB allocated for a PT-RS port, where both a PT-RS port and a DMRS port are configured for the UE, in accordance with one embodiment of the present disclosure. Here, the term “node” is used to refer to an apparatus performing the method, which may be either a UE or a network node. As shown, for each RB of one or more RBs allocated for a PT-RS port configured for the UE, the node determines a PT-RS subcarrier offset for the PT-RS port from a table (e.g., an UL table or a DL table) based on the DMRS port associated with the PT-RS port and the DMRS configuration type configured for the UE, where the PT-RS port is associated with a PDSCH or PUSCH with more than six spatial layers, and the DMRS type is an extended DMRS type supporting at least eight DMRS ports in a single OFDM symbol (step 500-B). The DMRS port associated with the PT-RS port is one of a plurality of DMRS ports, eight of the plurality of DMRS ports being associated with a first DMRS configuration type and twelve of the plurality of DMRS ports being associated with a second DMRS configuration type. Furthermore, each row of the table is associated with one of the plurality of DMRS ports and specifies different PT-RS subcarrier offsets for the PT-RS port associated with one of the plurality of DMRS ports for different resource element offset parameter values ​​for at least one of the first DMRS configuration type and the second DMRS configuration type. The node transmits or receives the PT-RS on the PT-RS port in each of one or more RBs according to the determined PT-RS subcarrier offsets (step 502-B). In one embodiment, the table is an uplink table, such as that of FIG. 2F, where the PT-RS is transmitted by the UE on the uplink and received by the network node.In another embodiment, the table is a downlink table, such as that of FIG. 2E, in which case the PT-RS is transmitted by the network node on the downlink and received by the UE. Additionally, the node may perform one or more actions related to orphan RBs for Type 1 DMRS (step 504-B). Details of such actions are described above and therefore will not be repeated here.

[0104] 5C illustrates a method in a wireless communication system for determining a per-layer phase tracking reference signal (PT-RS) to physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) power ratio per resource element (RE), where both a PT-RS port and a Rel18 DMRS port are configured for a UE and a PDSCH or PUSCH is scheduled with up to eight layers. The method includes: determining a per-layer PT-RS to PDSCH power ratio per RE for a PDSCH scheduled with seven and eight layers according to a table (500-C); determining a per-layer PT-RS to PUSCH power ratio per RE for a partially coherent codebook that is either PT-RS port-specific or common to all PT-RS ports (502-C); and, if PT-RS port-specific, determining the ratio for each PT-RS port according to both the number of scheduled PUSCH layers associated with the PT-RS port and the total number of scheduled PT-RS ports configured for PUSCH. In the case of a common T-RS port, the method includes one or more of: determining the ratio for a given number of scheduled PUSCH layers based on a predefined table for a given number of antenna port groups and / or a given number of scheduled PT-RS ports; determining a per-layer PT-RS-to-PUSCH power ratio per RE by the number of scheduled PUSCH layers for a fully coherent codebook (504-C); and / or determining a per-layer PT-RS-to-PUSCH power ratio per RE by the configured PT-RS port for the PUSCH for a non-coherent codebook (506-C). The steps may be performed in any combination and in any order.

[0105] 5D illustrates the operation of a transmitting node (i.e., a UE in the uplink case, or a network node (e.g., a base station or gNB) in the downlink case) according to one embodiment of the present disclosure. The transmitting node determines a PT-RS-to-PxSCH power ratio per spatial layer per RE for a PT-RS port associated with a scheduled PxSCH transmission for the UE, where the PxSCH transmission has up to eight spatial layers (step 500-D). Note that "PxSCH" as used herein is a general term referring to either a PDSCH or a PUSCH. The transmitting node determines the PT-RS-to-PxSCH power ratio per spatial layer per RE for a PT-RS port associated with a scheduled PxSCH transmission according to any of the embodiments for doing so described above. The transmitting node transmits the scheduled PxSCH transmission (step 502-D) and transmits the PT-RS on the PT-RS port in each RE assigned to the PT-RS port along with the scheduled PxSCH transmission and at a transmit power in accordance with the determined PT-RS to PxSCH power ratio per spatial layer per RE (step 504-D).

[0106] FIG. 6 illustrates an example of a communication system 600, according to some embodiments.

[0107] In this example, the communications system 600 includes a communications network 602 including an access network 604, such as a radio access network (RAN), and a core network 606 including one or more core network nodes 608. The access network 604 includes one or more access network nodes (one or more of which may be generally referred to as network nodes 610), such as network nodes 610A and 610B, or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP access points (APs). The network nodes 610 facilitate direct or indirect connectivity of user equipment (UE), such as by connecting UEs 612A, 612B, 612C, and 612D (one or more of which may be generally referred to as UEs 612), to the core network 606 over one or more wireless connections.

[0108] Exemplary wireless communication over a wireless connection includes sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in various embodiments, communication system 600 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, whether via a wired or wireless connection. Communication system 600 may include and / or interface with any type of communication, telecommunication, data, cellular, wireless network, and / or other similar type systems.

[0109] The UE 612 may be any of a wide variety of communication devices, including a wireless device configured, configured, and / or operable to communicate wirelessly with the network node 610 and other communication devices. Similarly, the network node 610 is configured, capable, configured, and / or operable to communicate, directly or indirectly, with the UE 612 and / or with other network nodes or equipment in the communication network 602 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration, in the communication network 602.

[0110] In the illustrated example, the core network 606 connects the network node 610 to one or more hosts, such as the host 616. These connections may be direct or indirect via one or more intermediate networks or devices. In other examples, the network node may be directly coupled to the host. The core network 606 includes one or more core network nodes (e.g., the core network node 608) structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, and therefore, those descriptions are generally applicable to the corresponding components of the core network node 608. Exemplary core network nodes include one or more of the following functions: a Mobile Switching Center (MSC), a Mobility Management Entity (MME), a Home Subscriber Server (HSS), an Access and Mobility Management Function (AMF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Subscription Identifier Deciphering Function (SIDF), a Unified Data Management (UDM), a Security Edge Protection Proxy (SEPP), a Network Publishing Function (NEF), and / or a User Plane Function (UPF).

[0111] The host 616 may be owned or under the control of, and operated by or on behalf of, a service provider other than the operator or provider of the access network 604 and / or the communication network 602. The host 616 may host various applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data about various ambient conditions detected by multiple UEs, analytics functions, social media, functions for controlling or possibly interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0112] Overall, the communication system 600 of FIG. 6 enables connectivity between UEs, network nodes, and hosts. In that sense, the communication system 600 may be configured to operate according to predefined rules or procedures, such as a particular standard, including, but not limited to, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable second, third, fourth, or fifth generation (2G, 3G, 4G, or 5G) standard, or any applicable future generation standard (e.g., sixth generation (6G)), a wireless local area network (WLAN) standard such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi), and / or any low power wide area network (LPWAN) standard such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, near field communications (NFC) ZigBee, LiFi, and / or LoRa and Sigfox.

[0113] In some examples, the communication network 602 is a cellular network that implements 3GPP standardized features. Thus, the communication network 602 may support network slicing to provide different logical networks to different devices connected to the communication network 602. For example, the communication network 602 may provide Ultra-Reliable Low Latency Communication (URLLC) services to some UEs, while providing enhanced Mobile Broadband (eMBB) services to other UEs and / or providing Massive Machine-Based Communication (mMTC) / Massive Internet of Things (IoT) services to still further UEs.

[0114] In some examples, the UE 612 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to the access network 604 on a predetermined schedule, when triggered by an internal or external event, or in response to a request from the access network 604. Furthermore, the UE may be configured to operate in a single or multi-radio access technology (RAT) or multi-standard mode. For example, the UE may operate with any one or a combination of Wi-Fi, New Radio (NR), and LTE, i.e., Multi-Radio Dual Connectivity (MR-DC), such as Enhanced UMTS Terrestrial RAN (E-UTRAN) NR-Dual Connectivity (EN-DC).

[0115] In this example, a hub 614 communicates with the access network 604 to facilitate indirect communication between one or more UEs (e.g., UEs 612C and / or 612D) and a network node (e.g., network node 610B). In some examples, the hub 614 may be a controller, a router, a content source, a content analyzer, or any of the other communication devices described herein with respect to UEs. For example, the hub 614 may be a broadband router that enables access to the core network 606 for the UE. As another example, the hub 614 may be a controller that sends commands or instructions to one or more actuators in the UE. The commands or instructions may be received from the UE, the network node 610, or may be due to executable code, scripts, processes, or other instructions in the hub 614. As another example, the hub 614 may be a data collector that serves as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 614 may be a content source. For example, for a UE that is a virtual reality (VR) headset, display, loudspeaker, or other media distribution device, the hub 614 may retrieve, via a network node, VR assets, video, audio, or other media or data related to sensory information, which the hub 614 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In yet another example, the hub 614 acts as a proxy server or orchestrator for the UEs, particularly in the case where one or more of the UEs are low-energy IoT devices.

[0116] The hub 614 may have a constant / permanent or intermittent connection to the network node 610B. The hub 614 may also enable different communication schemes and / or schedules between the hub 614 and the UEs (e.g., UEs 612C and / or 612D) and between the hub 614 and the core network 606. In other examples, the hub 614 is connected to the core network 606 and / or one or more UEs via a wired connection. Moreover, the hub 614 may be configured to connect to a machine-to-machine (M2M) service provider over the access network 604 and / or to another UE over a direct connection. In some scenarios, a UE may establish a wireless connection with the network node 610 while still connected via a wired or wireless connection through the hub 614. In some embodiments, the hub 614 may be a dedicated hub, i.e., a hub whose primary function is to route communications from / to the UE to / from the network node 610B. In other embodiments, the hub 614 may be a non-dedicated hub, i.e., a device that is capable of operating to route communications between the UE and the network node 610B, but that is further capable of operating as a communication initiation and / or termination point for some data channels.

[0117] 7 illustrates a UE 700, according to some embodiments. As used herein, a UE refers to a device capable of, set up, configured, and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smartphone, a mobile phone, a cell phone, a Voice over Internet Protocol (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless camera, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop computer, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a smart device, a wireless customer premises equipment (CPE), a vehicle-mounted or vehicle-embedded / integrated wireless device, etc. Other examples include any UE identified by 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0118] A UE may support device-to-device (D2D) communications, for example, by implementing 3GPP standards for sidelink communications, dedicated short-range communications (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE does not necessarily have a user in the sense of a human user who owns and / or operates an associated device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended for sale to or operation by a human user, but may not be associated with or initially associated with a particular human user. Alternatively, a UE may represent a device (e.g., a smart power meter) that is not intended for sale to or operation by an end user, but may be associated with or operated for the user's benefit.

[0119] The UE 700 includes a processing circuit 702 operably coupled to an input / output interface 706, a power source 708, a memory 710, a communication interface 712, and / or any other components, or any combination thereof, via a bus 704. Some UEs may utilize all or a subset of the components shown in FIG. 7. The level of integration between components may vary from UE to UE. Additionally, some UEs may include multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0120] The processing circuit 702 is configured to process instructions and data and may be configured to implement any sequential state machine operable to execute instructions stored in memory 710 as a machine-readable computer program. The processing circuit 702 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc.), programmable logic together with appropriate firmware, one or more stored computer programs such as a microprocessor or digital signal processor (DSP) together with appropriate software, a general-purpose processor, or any combination of the above. For example, the processing circuit 702 may include multiple central processing units (CPUs).

[0121] In this example, the input / output interface 706 may be configured to provide one or more interfaces to an input device, an output device, or one or more input and / or output devices. Examples of output devices include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smart card, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 700. Examples of input devices include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. A presence-sensitive display may include a capacitive or resistive touch sensor for detecting input from a user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, a light sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as the input device. For example, a universal serial bus (USB) port may be used to accommodate input and output devices.

[0122] In some embodiments, the power source 708 is structured as a battery or battery pack. Other types of power sources may be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery. The power source 708 may further include power circuitry for delivering power to various portions of the UE 700 from the power source 708 itself and / or from an external power source via an interface such as an input circuit or a power cable. Delivering power may be for charging the power source 708, for example. The power circuitry may perform any formatting, conversion, or other modification on the power from the power source 708 to make it suitable for the respective component of the UE 700 being powered.

[0123] The memory 710 may be or be configured to include memory, such as random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrical EPROM (EEPROM), magnetic disk, optical disk, hard disk, removable cartridge, flash drive, etc. In one example, the memory 710 includes one or more application programs 714, such as an operating system, a web browser application, a widget, a gadget engine, or other applications, and corresponding data 716. The memory 710 may store any of a variety of different operating systems or combinations of operating systems for use by the UE 700.

[0124] The memory 710 may be configured to include several physical drive units, such as a redundant array of independent disks (RAID), flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disc (HD-DVD) optical disc drive, an internal hard disk drive, a Blu-ray optical disc drive, a holographic digital data storage (HDDS) optical disc drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro-DIMM SDRAM, a smart card memory, such as a tamper-resistant module in the form of a universal integrated circuit card (UICC) containing one or more SIMs, such as a universal subscriber identity module (SIM) (USIM) and / or an Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC, commonly known as a "SIM card." The memory 710 may enable the UE 700 to access, offload, or upload data, instructions, application programs, etc. stored on a temporary or non-transitory memory medium. An article of manufacture, such as an article of manufacture utilizing a communication system, may be tangibly embodied as or in the memory 710, which may be or comprise a device-readable storage medium.

[0125] The processing circuit 702 may be configured to communicate with an access network or other networks using a communication interface 712. The communication interface 712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 722. The communication interface 712 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or network node in the access network). Each transceiver may include a transmitter 718 and / or a receiver 720 suitable for providing network communication (e.g., optical, electrical, frequency allocation, etc.). Moreover, the transmitter 718 and receiver 720 may be coupled to one or more antennas (e.g., antenna 722) and may share circuit components, software, or firmware, or may alternatively be implemented separately.

[0126] In the illustrated embodiment, the communication capabilities of communication interface 712 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, NFC, location-based communication such as using a Global Positioning System (GPS) to determine location, another similar communication capability, or any combination thereof. Communications may be implemented in accordance with one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), etc.

[0127] Regardless of the type of sensor, the UE may provide an output of data captured by the UE's sensors to a network node through the UE's communications interface 712 or via a wireless connection. Data captured by the UE's sensors may be communicated to a network node via another UE through a wireless connection. The output may be periodic (e.g., once every 15 minutes when reporting sensed temperature), in response to a triggering event (e.g., an alert is sent when humidity is detected), in response to a request (e.g., a user-initiated request), random (e.g., to even out the load from reporting from several sensors), or a continuous stream (e.g., a live video feed of a patient).

[0128] As another example, the UE may include an actuator, motor, or switch associated with a communications interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the state of the actuator, motor, or switch may change. For example, the UE may include a motor that adjusts a control surface or rotor of a drone in flight according to the received input, or a robotic arm that performs a medical procedure according to the received input.

[0129] When in the form of an IoT device, the UE may be a device for use in one or more application areas, including, but not limited to, urban wearable technology, augmented industrial applications, and healthcare. Non-limiting examples of such IoT devices are devices that are or are embedded in a connected refrigerator or freezer, a television, a connected lighting device, an energy meter, a robotic vacuum cleaner, a voice-controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a water inundation / humidity sensor, an electric door lock, a connected doorbell, an air conditioning system such as a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for augmented reality (AR) or VR, a wearable for haptic augmentation or sensory augmentation, a water sprinkler, an animal or product tracking device, a sensor for monitoring plants or animals, an industrial robot, an unmanned aerial vehicle (UAV), and any type of medical device such as a heart rate monitor or a remote-controlled surgical robot. A UE in the form of an IoT device comprises, in addition to the other components described with respect to the UE 700 shown in FIG. 7, circuitry and / or software depending on the intended application of the IoT device.

[0130] As yet another particular example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits results of such monitoring and / or measurements to another UE and / or network node. The UE may in this case be an M2M device, which may be referred to as an MTC device in a 3GPP context. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, bus, truck, ship, airplane, or other equipment capable of monitoring and / or reporting on its operating status or other functionality associated with its operation.

[0131] In practice, any number of UEs may be used together for a single use case. For example, a first UE may be a drone or be integrated in a drone and provide the drone's speed information (obtained through a speed sensor) to a second UE that is a remote controller that operates the drone. When a user makes changes from the remote controller, the first UE may adjust a throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UE may also include two or more of the functions described above. For example, a UE may include a sensor and an actuator and handle communication of data for both the speed sensor and the actuator.

[0132] 8 illustrates a network node 800 according to some embodiments. As used herein, a network node refers to a device capable of, set up, configured, and / or operable to communicate, directly or indirectly, with UEs and / or other network nodes or devices in a communication network. Examples of network nodes include, but are not limited to, APs (e.g., wireless APs), base stations (BSs) (e.g., wireless BSs, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).

[0133] BSs may be categorized based on the amount of coverage they provide (or, stated another way, their transmit power level) and may therefore be referred to as femto BSs, pico BSs, micro BSs, or macro BSs depending on the amount of coverage provided. A BS may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed wireless BS, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such RRUs may or may not be integrated with an antenna, such as an antenna-integrated radio. Portions of a distributed wireless BS may also be referred to as nodes in a distributed antenna system (DAS).

[0134] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, MSR equipment such as a multi-standard radio (MSR) BS, a network controller such as a radio network controller (RNC) or a BS controller (BSC), a base transceiver station (BTS), a transmission point, a transmitting node, a multi-cell / multicast coordination entity (MCE), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile location center (E-SMLC)), and / or a minimization drive test (MDT).

[0135] The network node 800 includes processing circuitry 802, memory 804, a communications interface 806, and a power source 808. The network node 800 may be assembled from multiple physically separate components (e.g., Node B and RNC components, or BTS and BSC components, etc.), each of which may have their own respective components. In some scenarios in which the network node 800 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple Node Bs. In such scenarios, each unique Node B and RNC pair may, in some cases, be considered a single separate network node. In some embodiments, the network node 800 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 804 for different RATs) and some components may be reused (e.g., antenna 810 may be shared by various RATs). Network node 800 may also include multiple sets of the various shown components for different wireless technologies, e.g., GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies, integrated into network node 800. These wireless technologies may be integrated into the same or different chips or sets of chips and other components within network node 800.

[0136] The processing circuitry 802 may comprise one or more combinations of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic operable to provide the network node 800 functionality, either alone or in conjunction with other network node 800 components such as memory 804.

[0137] In some embodiments, the processing circuit 802 comprises a system on a chip (SOC). In some embodiments, the processing circuit 802 includes one or more of a radio frequency (RF) transceiver circuit 812 and a baseband processing circuit 814. In some embodiments, the RF transceiver circuit 812 and the baseband processing circuit 814 may be on separate chips (or sets of chips), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuit 812 and the baseband processing circuit 814 may be on the same chip or set of chips, board, or unit.

[0138] The memory 804 may comprise any form of volatile or non-volatile computer-readable memory, including, but not limited to, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disc (CD), or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable, and / or computer-executable memory device that stores information, data, and / or instructions that may be used by the processing circuit 802. The memory 804 may store any suitable instructions, data, or information, including applications including one or more of computer programs, software, logic, rules, code, tables, and / or other instructions that can be executed by the processing circuit 802 and utilized by the network node 800. The memory 804 may be used to store computations performed by the processing circuit 802 and / or data received via the communications interface 806. In some embodiments, the processing circuit 802 and the memory 804 are integrated.

[0139] The communication interface 806 is used in wired or wireless communication of signaling and / or data between network nodes, access networks, and / or the UE. As shown, the communication interface 806 comprises port(s) / terminal(s) 816 for sending and receiving data to and from a network, e.g., over a wired connection. The communication interface 806 also includes radio front-end circuitry 818, which is coupled to an antenna 810 or, in some embodiments, may be part of the antenna 810. The radio front-end circuitry 818 comprises a filter 820 and an amplifier 822. The radio front-end circuitry 818 may be connected to the antenna 810 and the processing circuit 802. The radio front-end circuitry 818 may be configured to condition signals communicated between the antenna 810 and the processing circuit 802. The radio front-end circuitry 818 may receive digital data to be sent to another network node or the UE via a wireless connection. The radio front-end circuitry 818 may convert the digital data into radio signals having appropriate channel and bandwidth parameters using a combination of filters 820 and / or amplifiers 822. The radio signals may then be transmitted via the antenna 810. Similarly, when receiving data, the antenna 810 may collect the radio signals, which are then converted into digital data by the radio front-end circuitry 818. The digital data may be passed to the processing circuitry 802. In other embodiments, the communication interface 806 may comprise different components and / or different combinations of components.

[0140] In some alternative embodiments, network node 800 does not include a separate radio front-end circuit 818; instead, processing circuit 802 includes the radio front-end circuitry and is connected to antenna 810. Similarly, in some embodiments, all or a portion of RF transceiver circuitry 812 is part of communication interface 806. In still other embodiments, communication interface 806 includes one or more ports or terminals 816, radio front-end circuitry 818, and RF transceiver circuitry 812 as part of a radio unit (not shown), and communication interface 806 communicates with baseband processing circuitry 814 that is part of a digital unit (not shown).

[0141] Antenna 810 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 810 may be coupled to radio front-end circuitry 818 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 810 is separate from network node 800 and connectable to network node 800 through an interface or port.

[0142] The antenna 810, the communication interface 806, and / or the processing circuit 802 may be configured to perform any receiving operation and / or some obtaining operation described herein as being performed by the network node 800. Any information, data, and / or signal may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 810, the communication interface 806, and / or the processing circuit 802 may be configured to perform any transmitting operation described herein as being performed by the network node 800. Any information, data, and / or signal may be transmitted to a UE, another network node, and / or any other network equipment.

[0143] The power supply 808 provides power to the various components of the network node 800 in a form suitable for each component (e.g., at the voltage and current levels required for each respective component). The power supply 808 may further comprise, or be coupled to, power management circuitry for supplying power to the components of the network node 800 for performing the functions described herein. For example, the network node 800 may be connectable to an external power source (e.g., a power grid or an electrical outlet) via an input circuit or interface, such as an electrical cable, whereby the external power source supplies power to the power circuitry of the power supply 808. As a further example, the power supply 808 may comprise a power source in the form of a battery or battery pack connected to or integrated in the power circuitry. The battery may provide backup power in the event that the external power source fails.

[0144] Embodiments of network node 800 may include additional components other than those shown in Figure 8 to provide certain aspects of the network node's functionality, including any of the functionality described herein and / or functionality necessary to support the subject matter described herein. For example, network node 800 may include user interface devices to enable input of information into network node 800 and output of information from network node 800. This may enable a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 800.

[0145] 9 is a block diagram of a host 900, which may be an embodiment of the host 616 of FIG. 6 in accordance with various aspects described herein. As used herein, the host 900 may be or comprise various combinations of hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or processing resources in a server farm. The host 900 may provide one or more services to one or more UEs.

[0146] The host 900 includes a processing circuit 902 operably coupled to an input / output interface 906, a network interface 908, a power supply 910, and a memory 912 via a bus 904. In other embodiments, other components may be included. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as FIGS. 7 and 8, and therefore, those descriptions are generally applicable to the corresponding components of the host 900.

[0147] The memory 912 may include one or more computer programs, including one or more host application programs 914 and data 916, which may include user data, e.g., data generated by the UE for the host 900 or data generated by the host 900 for the UE. An embodiment of the host 900 may utilize only a subset or all of the shown components. The host application programs 914 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UE (e.g., handsets, desktop computers, wearable display systems, and heads-up display systems). The host application program 914 may also provide user authentication and license checks, and may periodically report health, route, and content availability to a central node, such as a device in the core network or a device on the edge of the core network. Thus, the host 900 may select and / or indicate a different host for over-the-top (OTT) services for the UE. The host application program 914 may support various protocols, such as HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (DASH or MPEG-DASH), etc.

[0148] FIG. 10 is a block diagram illustrating a virtualization environment 1000 in which functionality implemented by some embodiments may be virtualized. In this context, virtualizing means creating a virtual version of an apparatus or device, which may include virtualizing a hardware platform, storage devices, and networking resources. Virtualization, as used herein, may apply to any device described herein, or components thereof, and relates to implementations in which at least a portion of functionality is implemented as one or more virtual components. Some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1000 hosted by one or more of the hardware nodes, such as a network node, a UE, a core network node, or a hardware computing device acting as a host. Furthermore, in embodiments in which the virtual node does not require wireless connectivity (e.g., to a core network node or host), the node may be fully virtualized.

[0149] An application 1002 (which may alternatively be referred to as a software instance, a virtual appliance, a network function, a virtual node, a virtual network function, etc.) is run in the virtualized environment 900 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0150] The hardware 1004 includes processing circuitry, memory that stores software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices described herein, such as network interfaces, input / output interfaces, etc. Software is executed by the processing circuitry to instantiate one or more virtualization layers 1006 (also referred to as a hypervisor or VM monitor (VMM)), provide VMs 1008A and 1008B (one or more of which may be referred to generically as VMs 1008), and / or implement any of the functions, features, and / or benefits described with respect to some embodiments described herein. The virtualization layer 1006 may present to the VMs 1008 a virtual operating platform that appears to be networking hardware.

[0151] The VMs 1008 may comprise virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer 1006. Various embodiments of the virtual appliance 1002 instance may be implemented on one or more of the VMs 1008, and the implementation may be done in various ways. Hardware virtualization is referred to in some contexts as network functions virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage that may be located in data centers and customer premises equipment.

[0152] In the context of NFV, a VM 1008 may be a software implementation of a physical machine that runs programs as if those programs were running on a physical, non-virtualized machine. Each VM 1008 and the portion of the hardware 1004 on which it runs, whether hardware dedicated to that VM and / or hardware shared by that VM with other ones of the VMs 1008, form a separate virtual network element. Further, in the context of NFV, a virtual network function is responsible for handling a particular network function running in one or more VMs 1008 on the hardware 1004 and corresponds to the application 1002.

[0153] The hardware 1004 may be implemented in a standalone network node with general or specific components. The hardware 1004 may implement some functions via virtualization. Alternatively, the hardware 1004 may be part of a larger cluster of hardware (e.g., as in a data center or CPE) where many hardware nodes cooperate and are managed via a management and orchestration 1010 that, among other things, oversees the lifecycle management of the application 1002. In some embodiments, the hardware 1004 is coupled to one or more radio units, each including one or more transmitters and one or more receivers, which may be coupled to one or more antennas. The radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with virtual components to provide a virtual node with wireless capabilities, such as a RAN or BS. In some embodiments, some signaling may be provided using a control system 1012, which may alternatively be used for communication between the hardware nodes and the radio units.

[0154] 11 shows a communication diagram of a host 1102 communicating with a UE 1106 via a network node 1104 over a partial wireless connection, according to some embodiments. Exemplary implementations according to various embodiments of a UE (such as UE 612A of FIG. 6 and / or UE 700 of FIG. 7), a network node (such as network node 610A of FIG. 6 and / or network node 800 of FIG. 8), and a host (such as host 616 of FIG. 6 and / or host 900 of FIG. 9) described in the previous paragraphs will now be described with reference to FIG. 11.

[0155] Similar to host 900, an embodiment of host 1102 includes hardware such as a communications interface, processing circuitry, and memory. Host 1102 also includes software stored on or accessible by host 1102 and executable by the processing circuitry. The software includes a host application that may be operable to provide services to a remote user, such as a UE 1106 connecting via an OTT connection 1150 extending between UE 1106 and host 1102. In providing services to a remote user, the host application may provide user data that is transmitted using the OTT connection 1150.

[0156] The network node 1104 includes hardware that enables the network node 1104 to communicate with the host 1102 and the UE 1106 over a connection 1160. The connection 1160 may be direct or may pass through one or more other intermediate networks, such as a core network (similar to the core network 606 of FIG. 6) and / or one or more public, private, or hosted networks. For example, the intermediate network may be a backbone network or the Internet.

[0157] The UE 1106 includes hardware and software stored on or accessible by the UE 1106 and executable by the UE's processing circuitry. The software includes a client application, such as a web browser or operator-specific "app," which, with the support of the host 1102, may be operable to provide services to a human or non-human user via the UE 1106. An executing host application on the host 1102 may communicate with an executing client application via an OTT connection 1150 that terminates at the UE 1106 and the host 1102. In providing services to the user, the UE's client application may receive request data from the host application and provide user data in response to the request data. The OTT connection 1150 may transfer both request data and user data. The UE's client application may interact with the user to generate user data that the UE's client application provides to the host application through the OTT connection 1150.

[0158] The OTT connection 1150 may extend via a connection 1160 between the host 1102 and the network node 1104 and via a wireless connection 1170 between the network node 1104 and the UE 1106 to provide connectivity between the host 1102 and the UE 1106. The connections 1160 and wireless connections 1170 over which the OTT connection 1150 may be provided are depicted abstractly to show communication between the host 1102 and the UE 1106 via the network node 1104, without explicit reference to intermediary devices and the precise routing of messages through these devices.

[0159] As an example of transmitting data over the OTT connection 1150, in step 1108, the host 1102 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1106. In other embodiments, the user data is associated with the UE 1106 sharing data with the host 1102 without explicit human interaction. In step 1110, the host 1102 initiates a transmission carrying the user data toward the UE 1106. The host 1102 may initiate the transmission in response to a request sent by the UE 1106. The request may be caused by human interaction with the UE 1106 or by the operation of a client application executing on the UE 1106. The transmission may proceed via the network node 1104 in accordance with the teachings of the embodiments described throughout this disclosure. Thus, in step 1112, the network node 1104 transmits the user data carried in the transmission initiated by the host 1102 to the UE 1106, in accordance with the teachings of embodiments described throughout this disclosure. In step 1114, the UE 1106 receives the user data carried in the transmission, which may be performed by a client application running on the UE 1106 associated with the host application executed by the host 1102.

[0160] In some examples, the UE 1106 executes a client application that provides user data to the host 1102. The user data may be provided in reaction or response to data received from the host 1102. Thus, in step 1116, the UE 1106 may provide the user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from a user via an input / output interface of the UE 1106. Regardless of the particular manner in which the user data is provided, the UE 1106 initiates transmission of the user data towards the host 1102 via the network node 1104 in step 1118. In step 1120, the network node 1104 receives the user data from the UE 1106 and initiates transmission of the received user data towards the host 1102, in accordance with the teachings of embodiments described throughout this disclosure. In step 1122, the host 1102 receives the user data carried in the transmission initiated by the UE 1106.

[0161] One or more of the various embodiments improve the performance of the OTT service provided to the UE 1106 using the OTT connection 1150, of which the wireless connection 1170 forms the final segment. More precisely, the teachings of these embodiments may improve, for example, data rates, latency, power consumption, etc., thereby providing benefits such as, for example, reduced user latency, relaxed restrictions on file sizes, improved content resolution, better responsiveness, extended battery life, etc.

[0162] In an exemplary scenario, factory status information may be collected and analyzed by the host 1102. As another example, the host 1102 may process audio and video data that may have been retrieved from UEs for use in creating maps. As another example, the host 1102 may collect and analyze real-time data to assist in controlling vehicular congestion (e.g., controlling traffic signals). As another example, the host 1102 may store surveillance video uploaded by UEs. As another example, the host 1102 may store or control access to media content, such as video, audio, VR or AR, that the host 1102 may broadcast, multicast, or unicast to UEs. As other examples, the host 1102 may be used for energy pricing, remote control of non-time-critical electrical loads to balance power generation needs, location services, presentation services (such as compiling diagrams, etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing, and / or transmitting data.

[0163] In some examples, measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve upon. There may further be optional network functionality for reconfiguring the OTT connection 1150 between the host 1102 and the UE 1106 in response to fluctuations in the measurement results. The measurement procedures and / or the network functionality for reconfiguring the OTT connection 1150 may be implemented in software and hardware in the host 1102 and / or the UE 1106. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1150 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above, or other physical quantities from which software can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 1150 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not directly change the operation of the network node 1104. Such procedures and functionality may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation time, latency, etc. by the host 1102. The measurements may be implemented in software causing messages, particularly empty or "dummy" messages, to be sent using the OTT connection 1150 while monitoring propagation time, errors, etc.

[0164] While the computing devices (e.g., UEs, network nodes, hosts) described herein may include the depicted combinations of hardware components, other embodiments may comprise computing devices with different combinations of components. It should be understood that these computing devices may comprise any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, transforming the obtained information to other information, comparing the obtained or transformed information to information stored in a network node, and / or performing one or more operations based on the obtained or transformed information and as a result of the processing making a decision. Moreover, while a component is illustrated as a single box located within a larger box or nested within multiple boxes, in reality the computing device may comprise multiple different physical components that make up the single depicted component, and functionality may be partitioned among the separate components. For example, a communications interface may be configured to include any of the components described herein, and / or the functionality of those components may be partitioned between the processing circuitry and the communications interface. In another example, non-computationally intensive functionality of any of such components may be implemented in software or firmware, and computationally intensive functionality may be implemented in hardware.

[0165] In some embodiments, some or all of the functionality described herein may be provided by a processing circuit executing instructions stored in a memory, which in some embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuit without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of these particular embodiments, the processing circuit may be configured to perform the described functionality, regardless of whether or not it executes instructions stored on a non-transitory computer-readable storage medium. Benefits provided by such functionality are not limited to the processing circuit alone or to other components of the computing device, but are enjoyed by the computing device as a whole and / or by end users and wireless networks generally.

[0166] Some exemplary embodiments of the present disclosure are as follows.

[0167] Group A Embodiments Embodiment 1: A method in a wireless communication system for assigning subcarrier offsets for a phase tracking reference signal (PT-RS) port in each resource block (RB) allocated for the PT-RS port, wherein when both a PT-RS port and a Rel18 DMRS port are configured for a user equipment (UE), the PT-RS port is associated with one of eight Type 1 DMRS ports or twelve Type 2 DMRS ports, and the method includes: For a given associated DMRS port and higher layer configuration of resource offset parameters, determining a PT-RS subcarrier offset from either an uplink UL table or a downlink DL table (step 500-A), where each table row is associated with the DMRS port with which the PT-RS is associated; Supporting PTRS for orphan RBs in the case of Type 1 DMRS by the user equipment (step 502-A); The method includes one or more of:

[0168] Embodiment 2: The method of embodiment 1, wherein the DMRS port is one of Type 1 or Type 2.

[0169] Embodiment 3: The method of embodiment 1, wherein the resource offset parameter is "resourceElementOffset".

[0170] Embodiment 4: A method in a wireless communication system for determining a per-layer Phase Tracking Reference Signal (PT-RS) to Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH) power ratio per resource element (RE), wherein both a PT-RS port and a Rel18 DMRS port are configured for a UE, and a PDSCH or PUSCH is scheduled with up to 8 layers, the method comprising: Determining a PT-RS to PDSCH power ratio per layer per RE for PDSCH scheduled with 7 and 8 layers according to a table (500-B); Determining a per-layer PT-RS to PUSCH power ratio per RE for the partially coherent codebook, which is either PT-RS port specific or common to all PT-RS ports (502-B); If PT-RS port specific, determining the ratio for each PT-RS port by both the number of scheduled PUSCH layers associated with the PT-RS port and the total number of scheduled PT-RS ports associated with PUSCHs; In the case of a common PT-RS port, determining the ratio for a given number of scheduled PUSCH layers based on a predefined table for a given number of antenna port groups and / or a given number of scheduled PT-RS ports; For a fully coherent codebook, determining a PT-RS to PUSCH power ratio per layer per RE depending on the number of scheduled PUSCH layers (504-B), and / or For non-coherent codebooks, determining the PT-RS to PUSCH power ratio per layer per RE depending on the number of scheduled PTs (506-B) The method includes one or more of:

[0171] Group B Embodiments Embodiment 5: A method performed by a network node, the method including any of the features of the embodiments of group A.

[0172] Embodiment 6: The method of any one of embodiments 1 to 5, further comprising obtaining user data and forwarding the user data to a host or user equipment.

[0173] Group C Embodiments Embodiment 7: A method performed by a user equipment, the method including any of the features of the embodiments of Group A.

[0174] Group D Embodiments Embodiment 8: A user equipment comprising a processing circuit configured to perform any of the steps recited in any one of the embodiments of Group C, and a power supply circuit configured to supply power to the processing circuit.

[0175] Embodiment 9: A network node, the network node comprising: a processing circuit configured to perform any of the steps recited in any one of the embodiments of Group B; and a power supply circuit configured to supply power to the processing circuit.

[0176] Embodiment 10: A user equipment (UE), the UE comprising: an antenna configured to send and receive radio signals; a radio front-end circuit connected to the antenna and a processing circuit and configured to condition signals communicated between the antenna and the processing circuit, the processing circuit configured to perform any of the steps described in any one of the embodiments of Group C; an input interface connected to the processing circuit and configured to enable information input to the UE to be processed by the processing circuit; an output interface connected to the processing circuit and configured to output information from the UE that has been processed by the processing circuit; and a battery connected to the processing circuit and configured to provide power to the UE.

[0177] Embodiment 11: A host configured to operate in a communication system for providing over-the-top (OTT) services, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), the UE comprising the communication interface and the processing circuitry, the communication interface and processing circuitry of the UE configured to perform any of the steps set forth in any one of the embodiments of Group V to receive the user data from the host.

[0178] Embodiment 12: The host of embodiment 11, wherein the cellular network further includes a network node configured to communicate with the UE to transmit user data from the host to the UE.

[0179] Embodiment 13: A host as described in embodiment 11 or 12, wherein the processing circuitry of the host is configured to execute a host application to thereby provide user data, the host application is configured to interact with a client application executing on the UE, and the client application is associated with the host application.

[0180] Embodiment 14: A method implemented by a host operating in a communication system further including a network node and a user equipment (UE), the method including providing user data for the UE and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations described in any one of the embodiments of Group C to receive the user data from the host.

[0181] Embodiment 15: The method of embodiment 14, further comprising: executing, at the host, a host application associated with the client application executing on the UE to receive user data from the UE.

[0182] Embodiment 16: The method of embodiment 15, further comprising: at the host, sending input data to a client application executing on the UE, the input data being provided by executing the host application; and the user data being provided by the client application in response to the input data from the host application.

[0183] Embodiment 17: A host configured to operate in a communication system for providing over-the-top (OTT) services, the host comprising: a processing circuit configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), the UE comprising a communication interface and a processing circuit, the communication interface and processing circuit of the UE being configured to perform any of the steps set forth in any one of the embodiments of Group C to transmit the user data to the host.

[0184] Embodiment 18: The host of embodiment 17, wherein the cellular network further includes a network node configured to communicate with the UE to transmit user data from the UE to the host.

[0185] Embodiment 19: A host as described in embodiment 17 or 18, wherein the processing circuitry of the host is configured to execute a host application to thereby provide user data, the host application is configured to interact with a client application executing on the UE, and the client application is associated with the host application.

[0186] Embodiment 20: A method implemented by a host configured to operate in a communication system further including a network node and a user equipment (UE), the method including receiving, at the host, user data transmitted by the UE to the host via the network node, and the UE performing any of the steps described in any one of the embodiments of Group C to transmit the user data to the host.

[0187] Embodiment 21: The method of embodiment 20, further comprising: executing, at the host, a host application associated with the client application executing on the UE to receive user data from the UE.

[0188] Embodiment 22: The method of embodiment 21, further comprising: in the host, sending input data to a client application executing on the UE, the input data being provided by executing the host application; and the user data being provided by the client application in response to the input data from the host application.

[0189] Embodiment 23: A host configured to operate in a communication system for providing over-the-top (OTT) services, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communications interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations described in any one of the embodiments of Group B to transmit the user data from the host to the UE.

[0190] Embodiment 24: The host of embodiment 23, wherein processing circuitry of the host is configured to execute a host application that provides user data, and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive transmissions of the user data from the host.

[0191] Embodiment 25: A method implemented in a host configured to operate in a communication system further including a network node and a user equipment (UE), the method including providing user data for the UE and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, the network node performing any of the operations described in any one of the embodiments of Group B to transmit the user data from the host to the UE.

[0192]

[0082] Embodiment 26: The method of embodiment 25, further comprising: at the network node, transmitting user data provided by the host for the UE.

[0193] Embodiment 27: The method of embodiment 25 or 26, wherein the user data is provided by executing a host application in the host that interacts with a client application running on the UE, and the client application is associated with the host application.

[0194] Embodiment 28: A communications system configured to provide over-the-top services, the communications system comprising a host, the host comprising processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top services, and a network interface configured to initiate transmission of the user data to a cellular network node for transmission to the UE, the network node having a communications interface and processing circuitry, the processing circuitry of the network node being configured to perform any of the operations described in any one of the embodiments of Group B to transmit the user data from the host to the UE.

[0195] Embodiment 29: The communication system of embodiment 28, further comprising a network node and / or user equipment.

[0196] Embodiment 30: A host configured to operate in a communication system for providing over-the-top (OTT) services, the host comprising: a processing circuit configured to initiate reception of user data; and a network interface configured to receive user data from a network node in a cellular network, the network node having a communication interface and a processing circuit, the processing circuit of the network node configured to perform any of the operations described in any one of the embodiments of Group B to receive user data from a user equipment (UE) for the host.

[0197] Embodiment 31: A host as described in embodiment 29 or 30, wherein the processing circuitry of the host is configured to execute a host application to thereby provide user data, the host application is configured to interact with a client application executing on the UE, and the client application is associated with the host application.

[0198] Embodiment 32: The host of embodiment 30 or 31, wherein initiating the reception of user data includes requesting the user data.

[0199] Embodiment 33: A method implemented by a host configured to operate in a communication system further including a network node and a user equipment (UE), the method including initiating, at the host, reception of user data from the UE, the user data originating from a transmission received by the network node from the UE, and the network node performing any of the steps described in any one of the embodiments of Group B to receive the user data from the UE for the host.

[0200]

[0082] Embodiment 34: The method of embodiment 33, further comprising, at the network node, transmitting the received user data to the host.

[0201] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure, and all such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

1. 1. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: For each resource block (RB) of one or more RBs assigned for a phase tracking reference signal (PT-RS) port configured for the UE, determining a PT-RS subcarrier offset for the PT-RS port from a table based on a Demodulation Reference Signal (DMRS) port associated with the PT-RS port, a DMRS configuration type, and a resource element offset parameter configured for the UE (500-A, 500-B); the DMRS port associated with the PT-RS port is one of a plurality of DMRS ports, eight of the plurality of DMRS ports being associated with a first DMRS configuration type and twelve of the plurality of DMRS ports being associated with a second DMRS configuration type; each row of the table is associated with one of the plurality of DMRS ports and specifies different PT-RS subcarrier offsets for a PT-RS port associated with the one of the plurality of DMRS ports for different resource element offset parameter values ​​for at least one of the first DMRS configuration type and the second DMRS configuration type; Determining PT-RS subcarrier offsets (500-A, 500-B); Transmitting or receiving a PT-RS on the PT-RS port in the RB according to the determined PT-RS subcarrier offset (502-B); A method comprising:

2. The table is an uplink table associated with a physical uplink shared channel (PUSCH) transmission, and the one or more RBs are N scheduled for PUSCH. ＲＢ 10. The method of claim 1, wherein the RB is a subset of ≥ 1 RB.

3. The plurality of DMRS ports include DMRS ports 0 to 17, and the uplink table includes: A row associated with DMRS port 8, said row comprising: a PT-RS subcarrier offset of 4 for a resource offset parameter value of '00' for the first DMRS configuration type; and a PT-RS subcarrier offset of 6 for a resource offset parameter value of '01' for the first DMRS configuration type; and a PT-RS subcarrier offset of 10 for a resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 0 for a resource offset parameter value of “11” for the first DMRS configuration type; The lines, A row associated with DMRS port 9, said row comprising: a PT-RS subcarrier offset of 6 for the resource offset parameter value of '00' for the first DMRS configuration type; and a PT-RS subcarrier offset of 8 for the resource offset parameter value of '01' for the first DMRS configuration type; and a PT-RS subcarrier offset of 0 for the resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 2 for the resource offset parameter value of “11” for the first DMRS configuration type; The lines, A row associated with a DMRS port 10, said row comprising: a PT-RS subcarrier offset of 5 for the resource offset parameter value of '00' for the first DMRS configuration type; and a PT-RS subcarrier offset of 7 for the resource offset parameter value of '01' for the first DMRS configuration type; and a PT-RS subcarrier offset of 11 for the resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 1 for the resource offset parameter value of “11” for the first DMRS configuration type; The lines, A row associated with a DMRS port 11, said row comprising: a PT-RS subcarrier offset of 7 for the resource offset parameter value of '00' for the first DMRS configuration type; and a PT-RS subcarrier offset of 9 for the resource offset parameter value of '01' for the first DMRS configuration type; and a PT-RS subcarrier offset of 1 for the resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 3 for the resource offset parameter value of “11” for the first DMRS configuration type; The lines, A row associated with a DMRS port 12, said row comprising: a PT-RS subcarrier offset of 6 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 7 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 0 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 1 for the resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with a DMRS port 13, said row comprising: a PT-RS subcarrier offset of 7 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 0 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 1 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 6 for the resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with a DMRS port 14, said row comprising: a PT-RS subcarrier offset of 8 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 9 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 2 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 3 for the resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with a DMRS port 15, said row comprising: a PT-RS subcarrier offset of 9 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 2 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 3 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 8 for the resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with a DMRS port 16, said row comprising: a PT-RS subcarrier offset of 10 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 11 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 4 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 5 for the resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with a DMRS port 17, said row comprising: a PT-RS subcarrier offset of 11 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 4 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 5 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 10 for the resource offset parameter value of “11” for the second DMRS configuration type; and Defines the line and The method of claim 2 , comprising:

4. The uplink table includes: A row associated with DMRS port 0, said row comprising: a PT-RS subcarrier offset of 0 for the resource offset parameter value of '00' for the first DMRS configuration type; and a PT-RS subcarrier offset of 2 for the resource offset parameter value of '01' for the first DMRS configuration type; and a PT-RS subcarrier offset of 6 for the resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 8 for the resource offset parameter value of “11” for the first DMRS configuration type; and a PT-RS subcarrier offset of 0 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 1 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 6 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 7 for the resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with DMRS port 1, said row comprising: a PT-RS subcarrier offset of 2 for the resource offset parameter value of '00' for the first DMRS configuration type; and a PT-RS subcarrier offset of 4 for the resource offset parameter value of '01' for the first DMRS configuration type; and a PT-RS subcarrier offset of 8 for the resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 10 for the resource offset parameter value of “11” for the first DMRS configuration type; and a PT-RS subcarrier offset of 1 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 6 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 7 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 0 for the resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with DMRS port 2, said row comprising: a PT-RS subcarrier offset of 1 for the resource offset parameter value of '00' for the first DMRS configuration type; and a PT-RS subcarrier offset of 3 for the resource offset parameter value of '01' for the first DMRS configuration type; and a PT-RS subcarrier offset of 7 for the resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 9 for the resource offset parameter value of “11” for the first DMRS configuration type; and a PT-RS subcarrier offset of 2 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 3 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 8 for the resource offset parameter value of 10 for the second DMRS configuration type; and a PT-RS subcarrier offset of 9 for the resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with DMRS port 3, said row comprising: a PT-RS subcarrier offset of 3 for the resource offset parameter value of '00' for the first DMRS configuration type; and a PT-RS subcarrier offset of 5 for the resource offset parameter value of '01' for the first DMRS configuration type; and a PT-RS subcarrier offset of 9 for the resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 11 for the resource offset parameter value of “11” for the first DMRS configuration type; and a PT-RS subcarrier offset of 3 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 8 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 9 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 2 for the resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with DMRS port 4, said row comprising: a PT-RS subcarrier offset of 4 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 5 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 10 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 11 for the resource offset parameter value of “11” for the second DMRS configuration type; and The lines, A row associated with DMRS port 5, said row comprising: a PT-RS subcarrier offset of 5 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 10 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 11 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 4 for the resource offset parameter value of “11” for the second DMRS configuration type; Defines the line and The method of claim 3 further comprising:

5. The table is a downlink table associated with a Physical Downlink Shared Channel (PDSCH) transmission, and the one or more RBs are N RBs scheduled for PDSCH. ＲＢ 10. The method of claim 1, wherein the RB is a subset of ≥ 1 RB.

6. The plurality of DMRS ports include DMRS ports 0 to 17, and the downlink table includes: A row associated with a DMRS port 1008, said row comprising: a PT-RS subcarrier offset of 4 for a resource offset parameter value of '00' for the first DMRS configuration type; and a PT-RS subcarrier offset of 6 for a resource offset parameter value of '01' for the first DMRS configuration type; and a PT-RS subcarrier offset of 10 for a resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 0 for a resource offset parameter value of “11” for the first DMRS configuration type; The lines, A row associated with a DMRS port 1009, said row comprising: a PT-RS subcarrier offset of 6 for the resource offset parameter value of '00' for the first DMRS configuration type; and a PT-RS subcarrier offset of 8 for the resource offset parameter value of '01' for the first DMRS configuration type; and a PT-RS subcarrier offset of 0 for the resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 2 for the resource offset parameter value of “11” for the first DMRS configuration type; The lines, A row associated with a DMRS port 1010, said row comprising: a PT-RS subcarrier offset of 5 for the resource offset parameter value of '00' for the first DMRS configuration type; and a PT-RS subcarrier offset of 7 for the resource offset parameter value of '01' for the first DMRS configuration type; and a PT-RS subcarrier offset of 11 for the resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 1 for the resource offset parameter value of “11” for the first DMRS configuration type; The lines, A row associated with a DMRS port 1011, said row comprising: a PT-RS subcarrier offset of 7 for the resource offset parameter value of '00' for the first DMRS configuration type; and a PT-RS subcarrier offset of 9 for the resource offset parameter value of '01' for the first DMRS configuration type; and a PT-RS subcarrier offset of 1 for the resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 3 for the resource offset parameter value of “11” for the first DMRS configuration type; The lines, A row associated with a DMRS port 1012, said row comprising: a PT-RS subcarrier offset of 6 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 7 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 0 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 1 for the resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with a DMRS port 1013, said row comprising: a PT-RS subcarrier offset of 7 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 0 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 1 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 6 for the resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with a DMRS port 1014, said row comprising: a PT-RS subcarrier offset of 8 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 9 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 2 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 3 for the resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with a DMRS port 1015, said row comprising: a PT-RS subcarrier offset of 9 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 2 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 3 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 8 for the resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with a DMRS port 1016, said row comprising: a PT-RS subcarrier offset of 10 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 11 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 4 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 5 for the resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with a DMRS port 1017, said row comprising: a PT-RS subcarrier offset of 11 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 4 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 5 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 10 for the resource offset parameter value of “11” for the second DMRS configuration type; and Defines the line and The method of claim 5 , comprising:

7. The uplink table includes: A row associated with a DMRS port 1000, said row comprising: a PT-RS subcarrier offset of 0 for the resource offset parameter value of '00' for the first DMRS configuration type; and a PT-RS subcarrier offset of 2 for the resource offset parameter value of '01' for the first DMRS configuration type; and a PT-RS subcarrier offset of 6 for the resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 8 for the resource offset parameter value of “11” for the first DMRS configuration type; and a PT-RS subcarrier offset of 0 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 1 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 6 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 7 for the resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with a DMRS port 1001, said row comprising: a PT-RS subcarrier offset of 2 for the resource offset parameter value of '00' for the first DMRS configuration type; and a PT-RS subcarrier offset of 4 for the resource offset parameter value of '01' for the first DMRS configuration type; and a PT-RS subcarrier offset of 8 for the resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 10 for the resource offset parameter value of “11” for the first DMRS configuration type; and a PT-RS subcarrier offset of 1 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 6 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 7 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 0 for the resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with a DMRS port 1002, said row comprising: a PT-RS subcarrier offset of 1 for the resource offset parameter value of '00' for the first DMRS configuration type; and a PT-RS subcarrier offset of 3 for the resource offset parameter value of '01' for the first DMRS configuration type; and a PT-RS subcarrier offset of 7 for the resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 9 for the resource offset parameter value of “11” for the first DMRS configuration type; and a PT-RS subcarrier offset of 2 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 3 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 8 for the resource offset parameter value of 10 for the second DMRS configuration type; and a PT-RS subcarrier offset of 9 for the resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with a DMRS port 1003, said row comprising: a PT-RS subcarrier offset of 3 for the resource offset parameter value of '00' for the first DMRS configuration type; and a PT-RS subcarrier offset of 5 for the resource offset parameter value of '01' for the first DMRS configuration type; and a PT-RS subcarrier offset of 9 for the resource offset parameter value of “10” for the first DMRS configuration type; and a PT-RS subcarrier offset of 11 for the resource offset parameter value of “11” for the first DMRS configuration type; and a PT-RS subcarrier offset of 3 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 8 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 9 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 2 for the resource offset parameter value of “11” for the second DMRS configuration type; The lines, A row associated with a DMRS port 1004, said row comprising: a PT-RS subcarrier offset of 4 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 5 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 10 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 11 for the resource offset parameter value of “11” for the second DMRS configuration type; and The lines, A row associated with a DMRS port 1005, said row comprising: a PT-RS subcarrier offset of 5 for the resource offset parameter value of '00' for the second DMRS configuration type; and a PT-RS subcarrier offset of 10 for the resource offset parameter value of '01' for the second DMRS configuration type; and a PT-RS subcarrier offset of 11 for the resource offset parameter value of “10” for the second DMRS configuration type; and a PT-RS subcarrier offset of 4 for the resource offset parameter value of “11” for the second DMRS configuration type; Defines the line and The method of claim 6 further comprising:

8. 8. The method of claim 1, wherein the PT-RS port is mapped to one DMRS subcarrier of the associated DMRS port in each of the one or more RBs assigned to the PT-RS port, and the one DMRS subcarrier to which the PT-RS port is mapped in each RB is defined as a function of the determined PT-RS subcarrier offset.

9. The method of any one of claims 1 to 8, wherein the PT-RS subcarrier offset is with respect to the subcarrier with the lowest frequency in each of the one or more RBs.

10. N ＲＢ For a PDSCH or PUSCH scheduled with (≧1) RBs, ＲＢ The corresponding subcarriers are arranged in a sequence from 0 to PTRS ports are numbered in ascending order up to N ＲＢ The subcarriers mapped in the RBs are is given by ・ is the PT-RS subcarrier offset, ・i=0, 1, 2, . .. .. ・K ＰＴ－ＲＳ is the frequency density of the PT-RS, and K ＰＴ－ＲＳ ∈{2, 4}, ・ is the RB offset for the PT-RS, is given by ・ is the number of subcarriers per RB, ・n ＲＮＴＩ is the RNTI associated with the DCI that schedules the transmission, 9. The method according to any one of claims 1 to 8.

11. 11. The method of claim 1, wherein the UE may be scheduled such that the number of consecutively scheduled RBs for the UE in the downlink is odd and only PT-RS subcarrier offsets in the range of 0 to 7, inclusive, are allowed.

12. 12. The method of claim 11, wherein the RB is scheduled for downlink and the determined PT-RS subcarrier offset is outside the allowed range of 0 to 7, inclusive, and based thereon, the UE assumes that a PT-RS is not present in the RB.

13. 12. The method of claim 11, wherein the RB is scheduled for downlink and the determined PT-RS subcarrier offset is outside the allowed range of 0 to 7, inclusive, and based thereon, the UE assumes that a PT-RS is not present in the RB with the lowest index among each set of consecutively scheduled RBs, and assumes that a PT-RS is present in the remaining RBs.

14. 12. The method of claim 11, wherein the RB is scheduled for downlink and the determined PT-RS subcarrier offset is outside the allowed range of 0 to 7, inclusive, and based thereon, the UE assumes that a PT-RS is not present in the RB if the RB is associated with an orphaned resource element.

15. 12. The method of claim 11, wherein the RB is scheduled for downlink and the determined PT-RS subcarrier offset is outside the allowed range of 0 to 7, inclusive, and based thereon, the UE does not transmit a PT-RS in the RB.

16. 12. The method of claim 11, wherein the RB is scheduled for downlink and the determined PT-RS subcarrier offset is outside the allowed range of 0 to 7, inclusive, and based thereon, the UE does not transmit a PT-RS in the RB with the highest index among each set of consecutively scheduled RBs, and transmits a PT-RS in the remaining RBs.

17. 12. The method of claim 11, wherein the RB is scheduled for downlink and the determined PT-RS subcarrier offset is outside the allowed range of 0 to 7, inclusive, and based thereon, the UE does not transmit a PT-RS in an RB with a lowest index among each set of consecutively scheduled RBs, and transmits a PT-RS in the remaining RBs.

18. 1. A user equipment (UE) for a wireless communication system, the UE comprising: For each resource block (RB) of one or more RBs assigned for a phase tracking reference signal (PT-RS) port configured for the UE, determining a PT-RS subcarrier offset for the PT-RS port from a table based on a Demodulation Reference Signal (DMRS) port associated with the PT-RS port, a DMRS configuration type, and a resource element offset parameter configured for the UE (500-A, 500-B); the DMRS port associated with the PT-RS port is one of a plurality of DMRS ports, eight of the plurality of DMRS ports being associated with a first DMRS configuration type and twelve of the plurality of DMRS ports being associated with a second DMRS configuration type; each row of the table is associated with one of a plurality of DMRS ports and specifies different PT-RS subcarrier offsets for a PT-RS port associated with the one of the plurality of DMRS ports for different resource element offset parameter values ​​for at least one of the first DMRS configuration type and the second DMRS configuration type; Determining PT-RS subcarrier offsets (500-A, 500-B); Transmitting or receiving a PT-RS on the PT-RS port in the RB according to the determined PT-RS subcarrier offset (502-B); A user equipment (UE) adapted to perform the following:

19. 19. The UE of claim 18, further adapted to perform the method of any one of claims 2 to 17.

20. A user equipment (UE) (700) for a wireless communication system, said UE (700) comprising: a communication interface (712) comprising a transmitter (718) and a receiver (720); a processing circuit (702) associated with said communication interface (712); and the processing circuit (702) transmits to the UE (700), for each RB of one or more resource blocks (RBs) assigned for a phase tracking reference signal (PT-RS) port configured for the UE: determining a PT-RS subcarrier offset for the PT-RS port from a table based on a Demodulation Reference Signal (DMRS) port associated with the PT-RS port, a DMRS configuration type, and a resource element offset parameter configured for the UE (500-A, 500-B); the DMRS port associated with the PT-RS port is one of a plurality of DMRS ports, eight of the plurality of DMRS ports being associated with a first DMRS configuration type and twelve of the plurality of DMRS ports being associated with a second DMRS configuration type; each row of the table is associated with one of a plurality of DMRS ports and specifies different PT-RS subcarrier offsets for a PT-RS port associated with the one of the plurality of DMRS ports for different resource element offset parameter values ​​for at least one of the first DMRS configuration type and the second DMRS configuration type; Determining PT-RS subcarrier offsets (500-A, 500-B); Transmitting or receiving a PT-RS on the PT-RS port in the RB according to the determined PT-RS subcarrier offset (502-B); A user equipment (UE) (700) configured to:

21. 21. The UE (700) of claim 20, wherein the processing circuitry (702) is further configured to cause the UE (700) to perform a method according to any one of claims 2 to 17.

22. 1. A method performed by a network node in a wireless communication system, the method comprising: For each resource block (RB) of one or more RBs allocated for a phase tracking reference signal (PT-RS) port configured for a user equipment (UE), determining a PT-RS subcarrier offset for the PT-RS port from a table based on a Demodulation Reference Signal (DMRS) port associated with the PT-RS port, a DMRS configuration type, and a resource element offset parameter configured for the UE (500-A, 500-B); the DMRS port associated with the PT-RS port is one of a plurality of DMRS ports, eight of the plurality of DMRS ports being associated with a first DMRS configuration type and twelve of the plurality of DMRS ports being associated with a second DMRS configuration type; each row of the table is associated with one of a plurality of DMRS ports and specifies different PT-RS subcarrier offsets for a PT-RS port associated with the one of the plurality of DMRS ports for different resource element offset parameter values ​​for at least one of the first DMRS configuration type and the second DMRS configuration type; Determining PT-RS subcarrier offsets (500-A, 500-B); Transmitting or receiving a PT-RS on the PT-RS port in the RB according to the determined PT-RS subcarrier offset (502-B); A method comprising:

23. 1. A method performed by a transmitting node in a wireless communication system, the method comprising: determining a phase tracking reference signal (PT-RS) to PxSCH power ratio per spatial layer per resource element (RE) for scheduled physical downlink / uplink shared channel (PxSCH) transmissions for a user equipment (UE), the PxSCH transmissions having up to eight spatial layers and on more than four antenna ports; transmitting the scheduled PxSCH transmission (502-D) having up to eight layers; transmitting (504-D) a PT-RS on a PT-RS port at a transmit power according to the determined PT-RS to PxSCH power ratio per spatial layer per RE together with the PxSCH transmission; A method comprising:

24. 24. The method of claim 23, wherein the PxSCH transmission is a physical downlink shared channel (PDSCH) transmission having seven or eight layers, the determined PT-RS to PxSCH power ratio per spatial layer per RE is a PT-RS to PDSCH power ratio per spatial layer per RE, and the transmitting node is a network node in the wireless communication system.

25. 25. The method of claim 24, wherein determining the PT-RS to PDSCH power ratio per spatial layer per RE for the scheduled PDSCH transmission (500-D) is based on a table that specifies multiple PT-RS to PDSCH power ratio values ​​per spatial layer per RE for a respective multiple number of PDSCH spatial layer values, wherein the multiple number of PDSCH spatial layer values ​​includes 1, 2, 3, 4, 5, 6, 7, and 8.

26. 26. The method of claim 25, wherein each of the one or more rows of the table corresponds to a value of a downlink PT-RS configuration parameter "EPRE-ratio", where "EPRE-ratio" is signaled from the network node to the UE and can have an integer value from 0 to 3.

27. The table is a PT-RS to PDSCH power ratio value per spatial layer per RE of 8.45 for the case where the PDSCH transmission consists of 7 spatial layers; The value of the PT-RS to PDSCH power ratio for each spatial layer for each of 9 REs when the PDSCH transmission consists of 8 spatial layers; 27. The method of claim 25 or 26, wherein:

28. The table is a PT-RS to PDSCH power ratio value per spatial layer per RE of 0 for the case where the PDSCH transmission consists of one spatial layer; a PT-RS to PDSCH power ratio value per spatial layer per 3 RE for the case where the PDSCH transmission consists of two spatial layers; a PT-RS to PDSCH power ratio value per spatial layer per RE of 4.77 for the case where the PDSCH transmission consists of three spatial layers; a PT-RS to PDSCH power ratio value per spatial layer per 6 RE for the case where the PDSCH transmission consists of four spatial layers; a PT-RS to PDSCH power ratio value per spatial layer per 7 RE for the case where the PDSCH transmission consists of 5 spatial layers; a PT-RS to PDSCH power ratio value per spatial layer per RE of 7.78 for the case where the PDSCH transmission consists of 6 spatial layers; 28. The method of claim 27, further defining:

29. 27. The method of claim 25 or 26, wherein the value of the PT-RS to PDSCH power ratio per spatial layer per RE for n (n=7, 8) PDSCH spatial layers in one of the one or more rows is given by 10 log 10(n).

30. 30. The method of claim 25, wherein determining the PT-RS to PDSCH power ratio per spatial layer per RE for the scheduled PDSCH transmission having seven or eight spatial layers (500-D) comprises determining a row in the table based on the configured parameter "EPRE-ratio" and determining a value of the PT-RS to PDSCH power ratio per spatial layer per RE in the determined row based on the number of spatial layers of the PDSCH.

31. 24. The method of claim 23, wherein the PxSCH transmission is a Physical Uplink Shared Channel (PUSCH) transmission having up to eight layers and on up to eight antenna ports at the UE, the determined PT-RS to PxSCH power ratio per spatial layer per RE is a PT-RS to PUSCH power ratio per spatial layer per RE, and the transmitting node is the UE.

32. 32. The method of claim 31 , wherein determining the PT-RS to PUSCH power ratio per spatial layer per RE for the scheduled PUSCH transmission (500-D) is based on a table specifying multiple PT-RS to PUSCH power ratio values ​​per spatial layer per RE for a respective multiple number of PUSCH spatial layer values, wherein the multiple numbers of PDSCH spatial layer values ​​include 1, 2, 3, 4, 5, 6, 7, and 8.

33. 33. The method of claim 32, wherein each of the one or more rows of the table corresponds to a value of an uplink configuration parameter "UL-PTRS-power" received by the UE from a network node.

34. For fully coherent PUSCH transmissions on the up to eight antenna ports, each of the multiple PT-RS-to-PUSCH power ratio values ​​per spatial layer per RE in at least one of the one or more rows in the table is calculated based on a respective number of PUSCH spatial layers associated with the PT-RS port, as defined by: where: is the PT-RS to PUSCH power ratio per spatial layer per RE, 34. The method of claim 33, wherein ∑ i = 1 i ...

35. For non-coherent PUSCH transmissions on the up to eight antenna ports, each spatial layer of the PUSCH transmission is transmitted on only one of the up to eight antenna ports, and each of the plurality of PT-RS-to-PUSCH power ratio values ​​per spatial layer per RE in at least one of the one or more rows in the table is calculated based on a number of PT-RS ports scheduled for the PUSCH, as defined by: where: is the PT-RS to PUSCH power ratio per spatial layer per RE, and Q ｐ 34. The method of claim 33, wherein ∑ i = 1 i ⁢ ... is the number of PT-RS ports scheduled for the PUSCH transmission.

36. For partially coherent PUSCH transmissions on the up to eight antenna ports, the up to eight antenna ports of the UE are divided into two or more antenna port groups, PUSCH transmissions in each of the groups are coherent, and each of the plurality of PT-RS to PUSCH power ratio values ​​per spatial layer per RE in at least one of the one or more rows in the table is calculated based on a respective number of PUSCH spatial layers in the same antenna group as the PT-RS, as defined by: where: is the PT-RS to PUSCH power ratio per spatial layer per RE, is the number of spatial layers of the PUSCH transmission transmitted in the same antenna port group as the PT-RS, and Q ｐ 34. The method of claim 33, wherein ∑ i = 1 i ⁢ ... is the number of PT-RS ports scheduled for the PUSCH transmission.

37. 37. The method of claim 32, wherein determining the PT-RS to PUSCH power ratio per spatial layer per RE for the scheduled PUSCH transmission (500-D) comprises: determining a row in the table based on the configured parameter "UL-PTRS-power" and whether the PUSCH transmission is fully coherent, non-coherent, or partially coherent; and determining a value of the PT-RS to PUSCH power ratio per spatial layer per RE based on the respective number of spatial layers of the PUSCH transmission on the antenna port associated with the PT-RS port.

38. A transmitting node (610, 612) for a wireless communication system, said transmitting node (610, 612) comprising: determining a phase tracking reference signal (PT-RS) to PxSCH power ratio per spatial layer per resource element (RE) for scheduled physical downlink / uplink shared channel (PxSCH) transmissions for a user equipment (UE), the PxSCH transmissions having up to eight spatial layers and on more than four antenna ports; transmitting the scheduled PxSCH transmission (502-D) having up to eight layers; transmitting (504-D) a PT-RS on a PT-RS port at a transmit power according to the determined PT-RS to PxSCH power ratio per spatial layer per RE together with the PxSCH transmission; a transmitting node (610, 612) adapted to:

39. A transmitting node (610, 612) according to claim 38, further adapted to perform the method according to any one of claims 24 to 37.

40. A transmitting node (610, 612, 700, 800) for a wireless communication system, said transmitting node (610, 612, 700, 800) comprising a processing circuit (702, 802), said processing circuit (702, 802) configured to cause said transmitting node (610, 612, 700, 800) to: determining a phase tracking reference signal (PT-RS) to PxSCH power ratio per spatial layer per resource element (RE) for scheduled physical downlink / uplink shared channel (PxSCH) transmissions for a user equipment (UE), the PxSCH transmissions having up to eight spatial layers and on more than four antenna ports; transmitting the scheduled PxSCH transmission (502-D) having up to eight layers; transmitting (504-D) a PT-RS on a PT-RS port at a transmit power according to the determined PT-RS to PxSCH power ratio per spatial layer per RE together with the PxSCH transmission; A transmitting node (610, 612, 700, 800) configured to perform the following.

Images