PT-RS enhancements 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) allocated for a configured Phase Tracking Reference Signal (PT-RS) port, determining, based on a Demodulation Reference Signal (DMRS) port associated with the PT-RS port, a DMRS configuration type configured for the UE, and a resource element offset parameter, one or more resource blocks (RBs) allocated for the PT-RS port. A PT-RS subcarrier offset for the PT-RS port is determined from the table. The associated DMRS port is one of the plurality of DMRS ports. Each row of the table is associated with one DMRS port, and for different resource element offset parameter values of at least one DMRS configuration type, different PT-RS subcarrier offsets are defined for PT-RS ports associated with the DMRS port. The method further includes, for each allocated RB, transmitting / receiving a PT-RS on the PT-RS port in the RB according to the determined PT-RS subcarrier offset.

Description

Related applications

[0001] This application claims the benefit of provisional patent application serial number 63 / 432,956, filed December 15, 2022, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0002] The present disclosure relates to wireless communication systems, and more particularly to Phase Tracking Reference Signals (PT-RS) in wireless communication systems. Background Art

[0003] The Third 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 organized into equally sized subframes of 1 millisecond (ms) each. 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), each subframe has only one slot, and each slot consists of 14 OFDM symbols.

[0004] Data scheduling in NR is usually based on time slots. Figure 1A An example with a 14-symbol slot is shown in , where the first two symbols contain the Physical Downlink Control Channel (PDCCH) and the remaining symbols contain the Physical Shared Data Channel, i.e., the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH).

[0005] NR supports different subcarrier spacing (SCS) values. The supported SCS values ​​(also known as different numerology sets) 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 resource block corresponds to 12 consecutive subcarriers. RBs are numbered starting with 0 at one end of the system bandwidth. Figure 1B The basic NR physical time-frequency resource grid is shown in FIG, where only one RB within a 14-symbol slot is shown. One OFDM subcarrier during one OFDM symbol interval forms one resource element (RE).

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

[0008] Similarly, uplink data transmission 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 contained in the uplink grant (such as modulation order, coding rate, uplink resource allocation, etc.). NRPT-RS

[0009] 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 for 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, which means that the DMRS and its associated PT-RS are transmitted using the same precoder, and that the modulation symbols for the PT-RS are taken from the DMRS regardless of the configured DMRS sequence. This means that there is no specific configuration of the PT-RS sequence, as it is borrowed from the DMRS.

[0010] In the DL, if a UE is scheduled with one codeword, the PT-RS antenna port is associated with the lowest-indexed DMRS antenna port assigned for the PDSCH. If a UE is scheduled with two codewords, the PT-RS antenna port is associated with the lowest-indexed DMRS antenna port assigned for the codeword with the higher MCS. If the MCS indexes of the two codewords are the same, the PT-RS antenna port is associated with the lowest-indexed DMRS antenna port assigned for codeword 0.

[0011] In the UL, for PUSCH scheduled by DCI format 0_0 or by activating DCI format 0_0, the UL PT-RS port is associated with DMRS port 0. For PUSCH 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 of 3GPP Technical Specification (TS) 38.214 (see, for example, v17.3.0).

[0012] The presence of PT-RS is indicated separately by radio resource control (RRC) signaling for UL and DL. The uplink and downlink PTRS configurations in 3GPP TS 38.331 v17.2.0 are Figure 1C is shown in .

[0013] Each user is configured with a maximum of two PT-RS ports (to support multi-panel transmission in the UL and multiple transmission and reception point (TRP) transmission in the DL). This is configured via maxNrofPorts. For multi-user multiple input multiple output (MU-MIMO) with type 2 DMRS, there are a total of up to six orthogonal PT-RS ports, and for type 1 DMRS, there are a total of up to four orthogonal PT-RS ports. The PT-RS port is precoded on the antenna port using the same precoder as the associated DMRS port. PT-RS is not mapped to resource elements used for DMRS, synchronization signal blocks (SSBs), channel state information reference signals (CSI-RS), etc.

[0014] In the case of 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 2nd symbol, and every 4th OFDM symbol, respectively) Frequency density: 1 / 2 and 1 / 4 (i.e., one PTRS subcarrier every 2nd physical resource block (PRB) and every 4th PRB, respectively)

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

[0016] PT-RS is restricted to being in the scheduled RBs. The RBs containing the PT-RS are derived as follows. For DL / UL unicast transmissions, the RB level offset is implicitly derived from the UE's Radio Network Temporary Identifier (RNTI) and the frequency density. The PT-RS is mapped on one DMRS subcarrier of the associated DMRS port in each allocated RB. In addition, 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 determined as in: i=0,1,2,… · is the subcarrier offset and is given in Table 7.4.1.2.2-1 of 3GPP TS 38.211 v17.2.0 (for DL) and Table 6.4.1.2.2.1-1 of 3GPP TS 38.211 v17.2.0 (for UL). The tables are reproduced below as Tables 1 and 2, where resourceElementOffset is a parameter configured by RRC. If resourceElementOffset is not configured, the column corresponding to 'offset00' should be used. ·K PT-RS is the frequency density of PT-RS, and K PT-RS ∈{2,4} · is the RB offset of PT-RS and is given by · is the number of subcarriers per RB ·N RB is the number of scheduled RBs ·n RNTI It is the RNTI associated with the DCI scheduled for transmission. Within each RB allocated for PT-RS, the subcarrier of PT-RS (also called resource element offset) is determined by the index of the associated DMRS port and the RRC configuration parameter resourceElementOffset.

[0017] Note that in the DL, DMRS antenna ports (the same case for PDSCH transmission) start at port index 1000, while in the UL, DMRS antenna ports (the same case for PUSCH transmission) start at 0. In NR, the same DMRS design is used for both PDSCH in the DL and PUSCH in the UL. For ease of discussion, relative DMRS numbering (i.e., DMRS ports starting from port 0) can be used in the following discussion for both DL and UL. In this case, it can be understood that for the DL, DMRS port k actually refers to DMRS port 1000+k in the DL. Table 1: Table 7.4.1.2.2-1 (Parameters) of TS 38.211v17.2.0 ) Table 2: Table 6.4.1.2.2.1-1 (Parameters) of TS 38.211v17.2.0 )

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

[0019] Figure 1D An example of a PTRS RE in a PTRS RB with a time domain density of 1 / 2 is shown in FIG, where the PTRS port is associated with type 1 DMRS port 1 and the RRC parameter resourceElementOffset is configured as 'offset10'. Figure 1D The left RB contains a single-symbol DMRS, and Figure 1D The RB on the right carries a double-symbol DMRS.

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

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

[0022] As mentioned above, two types of DMRS for PDSCH and PUSCH are supported in NR, namely Type 1 and Type 2. The maximum number of DMRS ports for Type 1 DMRS is 4 for single-symbol DMRS and 8 for dual-symbol DMRS. For Type 2 DMRS, the maximum number of DMRS ports is 6 for single-symbol DMRS and 12 for dual-symbol DMRS.

[0023] DMRS ports are organized into code division multiplexing (CDM) groups. For Type 1 DMRS, there are two CDM groups: Group 0 and Group 1. In each RB of 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. For Type 2 DMRS, in each RB, there are three CDM groups, each consisting of two pairs of REs. Figure 1E An example is shown in .

[0024] Each CDM group includes two DMRS ports for single-symbol DMRS, and the two DMRS ports are multiplexed using a frequency-domain orthogonal cover code of length 2 (FD-OCC2). The number of DMRS ports is doubled when configuring dual-symbol DMRS, where in addition to FD-OCC2, a time-domain (TD) OCC of length 2 (TD-OCC2) is also used across two OFDM symbols. The details are described in clauses 6.4.1.1 and 7.4.1.1 of 3GPP TS38.211. The relationship between CDM groups and DMRS ports for PUSCH is described in Figure 2A (for Type 1 DMRS) and Figure 2B (for Type 2 DMRS). By simply changing the port Replace with The same applies to PDSCH DMRS.

[0025] An important aspect is that when TD-OCC is used for DMRS, PT-RS is not scheduled. Therefore, for PDSCH, when DMRS ports 1004-1007 are used for DMRS type 1, and when DMRS ports 1006-1011 are used for DMRS type 2, PT-RS will never appear. The same situation applies to DMRS for PUSCH. PT-RS power allocation

[0026] When PDSCH contains more than one spatial layer, the PT-RS transmission power can be increased. In other words, the ratio of the PT-RS energy per resource element (EPRE) of each layer to the PDSCH EPRE (ρ PTRS ) may be greater than 0 decibels (dB). This is because, for PT-RS, only a single layer is transmitted, while PDSCH can have multiple layers. For the same total EPRE, when PDSCH has more than one layer, the EPRE per layer of PT-RS can be greater than the EPRE per layer of PDSCH.

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

[0028] Similarly, when a UE is scheduled with Q p = {1,2} PT-RS ports, and the number of scheduled layers is When the PUSCH and PT-RS power ratio per RE per layer is pass is given, where if the higher layer parameter ptrs-Power is configured, then This is shown in Table 6.2.3.1-3 of 3GPP TS 38.214 v17.2.0 (reproduced herein as Table 4).

[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 TS 38.314. Table 4: Reproduction of Table 6.2.3.1-3 of TS 38.214 (factors related to PUSCH to PT-RS power ratio per RE per layer) )

[0030] In NR Rel-18, by introducing a frequency domain (FD) OCC code of length 4 in each CDM group, the number of DMRS ports per CDM group will be doubled for Type 1 and Type 2 DMRS, as shown in Figure 2C For Type 1 DMRS and Figure 2D The same applies to PDSCH DMRS (by simply changing the port Replace with ). Summary of the Invention

[0031] Disclosed are systems and methods related to 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 of one or more resource blocks (RBs) allocated for a PT-RS port configured for the UE, determining, from a table, a PT-RS subcarrier offset for the PT-RS port based on a DMRS port associated with the PT-RS port, a DMRS configuration type configured for the UE, and a resource element offset parameter. The DMRS port associated with the PT-RS port is one of a plurality of DMRS ports, wherein eight of the plurality of DMRS ports are associated with a first DMRS configuration type, and twelve of the plurality of DMRS ports are associated with a second DMRS configuration type. Each row of the table is associated with one of the multiple DMRS ports, and for different resource element offset parameter values ​​of at least one DMRS configuration type among the first DMRS configuration type and the second DMRS configuration type, a different PT-RS subcarrier offset is defined for the PT-RS port associated with the one of the multiple DMRS ports. The method further includes: for each of the one or more RBs allocated 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 way, by allocating appropriate subcarrier offsets, phase tracking with PT-RS of a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) with up to eight layers can be achieved.

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

[0033] In one embodiment, the uplink table further includes: A row associated with DMRS port 0, which defines: o For the first DMRS configuration type, the resource offset parameter value is '00', and the PT-RS subcarrier offset is 0; o For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 2; o For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 6; o For the first DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 8; o For the second DMRS configuration type, the resource offset parameter value is '00', and the PT-RS subcarrier offset is 0; o For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 1; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 6; and o For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 7; A row associated with DMRS port 1, which defines: o For the first DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 2; o For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 4; o For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 8; o For the first DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 10; o For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 1; o For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 6; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 7; and o For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 0; A row associated with DMRS port 2, which defines: o For the first DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 1; o For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 3; o For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 7; o For the first DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 9; o For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 2; o For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 3; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 8; and o For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 9; A row associated with DMRS port 3, which defines: o For the first DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 3; o For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 5; o For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 9; o For the first DMRS configuration type, the resource offset parameter value is '11', and the PT-RS subcarrier offset is 11; o For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 3; o For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 8; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 9; and o For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 2; A row associated with DMRS port 4, which defines: o For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 4; o For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 5; o For the second DMRS configuration type, the resource offset parameter value is '10', and the PT-RS subcarrier offset is 10; and o For the second DMRS configuration type, the resource offset parameter value is '11', and the PT-RS subcarrier offset is 11; and A row associated with DMRS port 5, which defines: o For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 5; o For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 10; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 11; and o For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 4.

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

[0035] In one embodiment, the uplink table further includes: A row associated with DMRS port 1000, which defines: o For the first DMRS configuration type, the resource offset parameter value is '00', and the PT-RS subcarrier offset is 0; o For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 2; o For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 6; o For the first DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 8; o For the second DMRS configuration type, the resource offset parameter value is '00', and the PT-RS subcarrier offset is 0; o For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 1; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 6; and o For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 7; A row associated with DMRS port 1001, which defines: o For the first DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 2; o For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 4; o For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 8; o For the first DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 10; o For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 1; o For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 6; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 7; and o For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 0; A row associated with DMRS port 1002, which defines: o For the first DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 1; o For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 3; o For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 7; o For the first DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 9; o For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 2; o For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 3; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 8; and o For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 9; A row associated with DMRS port 1003, which defines: o For the first DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 3; o For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 5; o For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 9; o For the first DMRS configuration type, the resource offset parameter value is '11', and the PT-RS subcarrier offset is 11; o For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 3; o For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 8; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 9; and o For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 2; A row associated with DMRS port 1004, which defines: o For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 4; o For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 5; o For the second DMRS configuration type, the resource offset parameter value is '10', and the PT-RS subcarrier offset is 10; and o For the second DMRS configuration type, the resource offset parameter value is '11', and the PT-RS subcarrier offset is 11; and A row associated with DMRS port 1005, which defines: o For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 5; o For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 10; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 11; and o For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 4.

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

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

[0038] In one embodiment, there are N RB (≥1) RBs of PDSCH or PUSCH, the N RB The corresponding The subcarriers are ordered from 0 to are numbered, and the N RB The subcarrier to which the PTRS port is mapped in an RB is given by: in: · 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} · is the RB offset of PT-RS and is given by · is the number of subcarriers per RB ·n RNTI is the RNTI associated with the DCI that schedules the transmission.

[0039] In one embodiment, the UE may be scheduled such that the number of RBs consecutively scheduled for the UE in the downlink is an odd number, and only PT-RS subcarrier offsets in the range of 0 to 7, inclusive, are allowed. In one embodiment, the RB is scheduled for the downlink, and the determined PT-RS subcarrier offset exceeds the allowed range of 0 to 7, inclusive, and based on this, the UE assumes that no PT-RS is present in the RB. In one embodiment, the RB is scheduled for the downlink, and the determined PT-RS subcarrier offset exceeds the allowed range of 0 to 7, inclusive, and based on this, the UE assumes that no PT-RS is present in the RB with the lowest index in each set of consecutively scheduled RBs and assumes that PT-RS is present in the remaining RBs. In one embodiment, the RB is scheduled for the downlink, and the determined PT-RS subcarrier offset exceeds the allowed range of 0 to 7, inclusive, and based on this, if the RB is associated with an orphan resource element, the UE assumes that no PT-RS is present in the RB. In one embodiment, the RB is scheduled for downlink, and the determined PT-RS subcarrier offset exceeds the allowed range of 0 to 7, inclusive, and based on this, the UE does not transmit the PT-RS in the RB. In one embodiment, the RB is scheduled for downlink, and the determined PT-RS subcarrier offset exceeds the allowed range of 0 to 7, inclusive, and based on this, the UE does not transmit the PT-RS in the RB with the highest index in each set of consecutively scheduled RBs, and transmits the PT-RS in the remaining RBs. In one embodiment, the RB is scheduled for downlink, and the determined PT-RS subcarrier offset exceeds the allowed range of 0 to 7, inclusive, and based on this, the UE does not transmit the PT-RS in the RB with the lowest index in each set of consecutively scheduled RBs, and transmits the 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 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 a DMRS port associated with the PT-RS port, a DMRS configuration type configured for the UE, and a resource element offset parameter. The DMRS port associated with the PT-RS port is one of a plurality of DMRS ports, wherein eight of the plurality of DMRS ports are associated with a first DMRS configuration type, and twelve of the plurality of DMRS ports are associated with a second DMRS configuration type. Each row of the table is associated with one of the plurality of DMRS ports, and defines different PT-RS subcarrier offsets for the PT-RS port associated with the one of the plurality of DMRS ports for different resource element offset parameter values ​​of at least one of the first DMRS configuration type and the second DMRS configuration type. The UE is further adapted to, for each of the one or more RBs allocated 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, by allocating appropriate subcarrier offsets, phase tracking with PT-RS for a PDSCH or PUSCH having up to eight layers can be achieved.

[0041] In one embodiment, a UE for a wireless communication system includes: a communication interface comprising 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 of one or more RBs allocated for a PT-RS port configured for the UE, determine, from a table, a PT-RS subcarrier offset for the PT-RS port based on a DMRS port associated with the PT-RS port, a DMRS configuration type configured for the UE, and a resource element offset parameter. The DMRS port associated with the PT-RS port is one of a plurality of DMRS ports, wherein eight of the plurality of DMRS ports are associated with a first DMRS configuration type and twelve of the plurality of DMRS ports are associated with a second DMRS configuration type. Each row of the table is associated with one of the plurality of DMRS ports, and defines different PT-RS subcarrier offsets for the 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 and second DMRS configuration types. The processing circuit is further configured to cause the UE to: for each of the one or more RBs allocated 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, by allocating appropriate subcarrier offsets, phase tracking with PT-RS for a PDSCH or PUSCH having up to eight layers can be achieved.

[0042] Also disclosed is a method performed by a network node in a wireless communication system. In one embodiment, the method includes determining, for each of one or more RBs allocated for a PT-RS port configured for the UE, a PT-RS subcarrier offset for the PT-RS port from a table based on a DMRS port associated with the PT-RS port, a DMRS configuration type configured for the UE, and a resource element offset parameter. The DMRS port associated with the PT-RS port is one of a plurality of DMRS ports, wherein eight of the plurality of DMRS ports are associated with a first DMRS configuration type and twelve of the plurality of DMRS ports are associated with a second DMRS configuration type. Each row of the table is associated with one of the plurality of DMRS ports, and defines different PT-RS subcarrier offsets for the PT-RS port associated with the one of the plurality of DMRS ports for different resource element offset parameter values ​​of at least one of the first DMRS configuration type and the second DMRS configuration type. The method further includes, for each of the one or more RBs allocated 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, by allocating appropriate subcarrier offsets, phase tracking with PT-RS for a PDSCH or PUSCH having up to eight layers can be achieved.

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

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

[0045] In one embodiment, determining the PT-RS to PDSCH power ratio per RE per spatial layer for the scheduled PDSCH transmission is based on a table, the table defining a plurality of PT-RS to PDSCH power ratio values ​​per RE per spatial layer for a corresponding plurality of numbers of PDSCH spatial layer values, wherein the plurality of numbers of PDSCH spatial layer values ​​comprises 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', wherein 'EPRE-ratio' is signaled from the network node to the UE and may have an integer value from 0 to 3.

[0046] In one embodiment, the table defines: for the case where the PDSCH transmission consists of 7 spatial layers, the PT-RS to PDSCH power ratio per RE per spatial layer is 8.45; and for the case where the PDSCH transmission consists of 8 spatial layers, the PT-RS to PDSCH power ratio per RE per spatial layer is 9. In one embodiment, the table further defines: for the case where the PDSCH transmission consists of 1 spatial layer, the PT-RS to PDSCH power ratio per RE per spatial layer is 0; for the case where the PDSCH transmission consists of 2 spatial layers, the PT-RS to PDSCH power ratio per RE per spatial layer is 3; for the case where the PDSCH transmission consists of 3 spatial layers, the PT-RS to PDSCH power ratio per RE per spatial layer is 4.77; for the case where the PDSCH transmission consists of 4 spatial layers, the PT-RS to PDSCH power ratio per RE per spatial layer is 6; for the case where the PDSCH transmission consists of 5 spatial layers, the PT-RS to PDSCH power ratio per RE per spatial layer is 7; for the case where the PDSCH transmission consists of 6 spatial layers, the PT-RS to PDSCH power ratio per RE per spatial layer is 7.78.

[0047] In one embodiment, the PT-RS to PDSCH power ratio per RE per spatial layer of 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 RE per spatial layer of the scheduled PDSCH transmission having 7 or 8 spatial layers includes determining a row in the table based on the configured parameter 'EPRE-ratio', and determining the PT-RS to PDSCH power ratio value per RE per spatial layer 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 at the UE having up to 8 layers and on up to 8 antenna ports, the determined PT-RS to PxSCH power ratio per RE per spatial layer is a PT-RS to PUSCH power ratio per RE per spatial layer, and the transmitting node is the UE.

[0050] In one embodiment, determining the PT-RS to PUSCH power ratio per RE per spatial layer for the scheduled PUSCH transmission is based on a table, the table defining a plurality of PT-RS to PUSCH power ratio values ​​per RE per spatial layer for a corresponding plurality of numbers of PUSCH spatial layer values, wherein the plurality of numbers of PUSCH 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 the at most 8 antenna ports, each of the plurality of PT-RS to PUSCH power ratio values ​​per RE per spatial layer in at least one of the one or more rows of the table is calculated based on the corresponding number of PUSCH spatial layers associated with the PT-RS port, as defined by the following formula: in, is the PT-RS to PUSCH power ratio per RE per spatial layer, and is the number of spatial layers in the PUSCH transmission. In one embodiment, for non-coherent PUSCH transmission on the at most 8 antenna ports, each spatial layer of the PUSCH transmission is transmitted on only one of the at most 8 antenna ports, and each of the plurality of PT-RS to PUSCH power ratio values ​​per RE per spatial layer 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 the following equation: in, is the PT-RS to PUSCH power ratio per RE per spatial layer, and Q pis the number of PT-RS ports scheduled for the PUSCH transmission. In one embodiment, for partially coherent PUSCH transmission on the at most 8 antenna ports, the at most 8 antenna ports of the UE are divided into two or more antenna port groups, and PUSCH transmissions in each of the groups are coherent, and each of the multiple PT-RS to PUSCH power ratio values ​​per RE per spatial layer in at least one of the one or more rows in the table is calculated based on a corresponding number of PUSCH spatial layers in the same antenna group as the PT-RS, as defined by the following formula: in, is the PT-RS to PUSCH power ratio per RE per spatial layer, is the number of spatial layers of the PUSCH 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 RE per spatial layer of the scheduled PUSCH transmission includes: determining the rows 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 the PT-RS to PUSCH power ratio value per RE per spatial layer based on the corresponding number of spatial layers of the PUSCH transmission on the antenna port associated with the PT-RS port.

[0052] A corresponding embodiment of a transmitting node for a wireless communication system is 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 RE per spatial layer for a scheduled PxSCH transmission for a UE, wherein the PxSCH transmission has up to 8 spatial layers and is on more than 4 antenna ports. The transmitting node is further adapted to transmit the scheduled PxSCH transmission having up to 8 layers and transmit a PT-RS on a PT-RS port along with the PxSCH transmission at a transmit power according to the determined PT-RS to PxSCH power ratio per RE per spatial layer.

[0053] In one embodiment, a transmitting node for a wireless communication system includes processing circuitry configured to cause the transmitting node to: determine a PT-RS to PxSCH power ratio per RE per spatial layer for a scheduled PxSCH transmission for a UE, wherein the PxSCH transmission has at most 8 spatial layers and is on more than 4 antenna ports. The processing circuitry is further configured to cause the transmitting node to: transmit the scheduled PxSCH transmission having at most 8 layers, and transmit a PT-RS on a PT-RS port along with the PxSCH transmission at a transmit power according to the determined PT-RS to PxSCH power ratio per RE per spatial layer. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] The accompanying drawings incorporated in and forming a part of this specification illustrate several aspects of the disclosure and together with the description serve to explain the principles of the disclosure.

[0055] Figure 1A An example of a New Radio (NR) timeslot is shown;

[0056] Figure 1B An example of a resource block (RB) in NR is shown;

[0057] Figure 1C shows the Phase Tracking Reference Signal (PT-RS) downlink and uplink configuration information elements defined in the 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 38.331 v17.2.0;

[0058] Figure 1D An example of a PT-RS resource element (RE) in a PT-RS RB with a time domain density of 1 / 2 is shown, where the PT-RS port is associated with type 1 demodulation reference signal (DMRS) port 1, and the radio resource control (RRC) parameter resourceElementOffset is configured as 'offset10', where there is a single symbol DMRS ( Figure 1D ), and there is a double-symbol DMRS ( Figure 1D on the right side);

[0059] Figure 1E Shown is a PT-RS port associated with a single symbol type 1 DMRS port 1 (in Figure 1E is shown on the left) and single symbol type 2 DMRS port 1 (on Figure 1E ), and both are with the RRC parameter resourceElementOffset configured as 'offset10', but with a PTRS time density of L=1;

[0060] Figure 2AThe relationship between the code division multiplexing (CDM) group and DMRS port of the physical uplink shared channel (PUSCH) for type 1 DMRS is shown;

[0061] Figure 2B The relationship between the CDM group and DMRS port for PUSCH of type 2 DMRS is shown;

[0062] Figure 2C Shown is the case where the number of DMRS ports per CDM group is doubled for Type 1 DMRS;

[0063] Figure 2D Shown is the case where the number of DMRS ports per CDM group is doubled for Type 2 DMRS;

[0064] Figure 2E shows an example of a table defining downlink PT-RS subcarrier offsets for an increasing number of DMRS ports for Type 1 and Type 2 DMRS according to one embodiment of the present disclosure;

[0065] Figure 2F shows an example of a table defining uplink PT-RS subcarrier offsets for an increasing number of DMRS ports for Type 1 and Type 2 DMRS according to one embodiment of the present disclosure;

[0066] Figure 3A 1 and 2. The diagram shows the antenna port corresponding to 'offset01' and DMRS according to an exemplary embodiment of the present disclosure. An example of an allowed combination of , in which case the subcarrier offset is

[0067] Figure 3B An example of a new parameter introduced in RRC for separately setting a downlink PT-RS subcarrier offset for Rel-18 DMRS compared to Rel-15 DMRS according to one embodiment of the present disclosure is shown;

[0068] Figure 3C An example of a new parameter introduced in RRC to set the uplink PT-RS subcarrier offset separately for Rel-18 DMRS compared to Rel-15 DMRS is shown;

[0069] Figure 4A-1 An example table is shown defining a PT-RS to PDSCH transmit power ratio per RE per layer for a PDSCH having up to eight spatial layers according to one embodiment of the present disclosure;

[0070] Figure 4A-2An example table is shown defining a PT-RS to PUSCH transmit power ratio per RE per layer for a PUSCH with up to eight spatial layers for a fully coherent codebook according to one embodiment of the present disclosure;

[0071] Figure 4A-3 An example is shown in which two PT-RS ports are scheduled according to an embodiment of the present disclosure and a 3 decibel (dB) power boost can be achieved for each of the PT-RS ports;

[0072] Figure 4A-4 An example table is shown defining a PT-RS to PUSCH transmit power ratio per RE per layer for a PUSCH with up to eight spatial layers for a non-coherent codebook according to one embodiment of the present disclosure;

[0073] Figure 4B-1 An example is shown in which a transmitting node has eight antenna ports divided into two antenna port groups;

[0074] Figure 4B-2 An example is shown in which a transmitting node has eight antenna ports divided into four antenna port groups;

[0075] Figure 4C-1 An example table is shown defining a transmit power ratio of PT-RS to PUSCH per RE per layer for a PUSCH having up to four spatial layers in the same antenna port group as a PT-RS port for a partially coherent codebook according to one embodiment of the present disclosure;

[0076] Figure 4C-2 An example of a hybrid partially coherent and non-coherent codebook is shown, where each PUSCH layer in port group 1 is transmitted on only a single antenna port, while each PUSCH layer scheduled in each of the other groups is transmitted on all antenna ports in that group;

[0077] Figure 4C-3 An example table is shown defining a transmit power ratio of PT-RS to PUSCH per RE per layer for a PUSCH having up to four spatial layers in the same antenna port group as a PT-RS port for a partially coherent codebook according to another embodiment of the present disclosure;

[0078] Figure 4C-4 An example of a PT-RS to PUSCH EPRE power ratio table for two antenna groups according to an embodiment of the present disclosure is shown, where the maximum number of PT-RS ports is equal to 2, i.e., Q p ∈{1,2};

[0079] Figure 4C-5An example of one or more entries of a PT-RS to PUSCHEPRE power ratio table for an 8TX UE with 4 antenna groups according to an embodiment of the present disclosure is shown, where the maximum number of PTRS ports is equal to 2, i.e., Q_p∈{1,2}, and each PT-RS port is associated with two antenna groups;

[0080] Figure 4C-6 shows example different PT-RS to PUSCH EPRE power ratio tables for different numbers of scheduled PTRS ports according to an embodiment of the present disclosure;

[0081] Figure 5A A method for allocating a subcarrier offset for a phase tracking reference signal (PT-RS) port in each resource block (RB) allocated for the PT-RS port in a wireless communication system is shown, wherein when both PT-RS and Rel 18 DMRS ports are configured for a user equipment (UE), the PT-RS port is associated with one of 8 Type 1 DMRS ports or 12 Type 2 DMRS ports;

[0082] Figure 5B is a flow chart illustrating an operation of a user equipment (UE) or a network node (e.g., a base station, such as, for example, a gNB) performing PT-RS subcarrier offset allocation for each RB allocated for a PT-RS port according to an embodiment of the present disclosure, wherein both PT-RS and DMRS ports are configured for the UE;

[0083] Figure 5C A method for determining a power ratio of a phase tracking reference signal (PT-RS) to a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) per resource element (RE) per layer in a wireless communication system is provided, wherein both PT-RS and Rel 18 DMRS ports are configured for a UE and PDSCH or PUSCH is scheduled with up to 8 layers.

[0084] Figure 5D The operation of a transmitting node (i.e., a UE in the case of uplink, or a network node (e.g., a base station or gNB) in the case of downlink) according to one embodiment of the present disclosure is illustrated;

[0085] Figure 6 shows an example of a communication system according to some embodiments;

[0086] Figure 7 illustrates a UE according to some embodiments;

[0087] Figure 8 illustrates a network node according to some embodiments;

[0088] Figure 9is a block diagram of a host computer according to various aspects described herein, which may be Figure 6 An embodiment of a host;

[0089] Figure 10 is a block diagram illustrating a virtualization environment in which functionality implemented by some embodiments may be virtualized; and

[0090] Figure 11 A communication diagram shows a host communicating with 1106 via a network node over a partially wireless connection in accordance with some embodiments. DETAILED DESCRIPTION

[0091] The embodiments described below represent information that enables those skilled in the art to practice these embodiments and illustrate the best way to practice these embodiments. After 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 mentioned herein. It should be understood that these concepts and applications all fall within the scope of the present disclosure.

[0092] There are certain challenges. In the existing New Radio (NR) up to Release 17, the Phase Tracking Reference Signal (PT-RS or PTRS) can be configured with a Physical Downlink Shared Channel (PDSCH) (with up to four layers of Type 1 Demodulation Reference Signal (DMRS) and up to six layers of Type 2 DMRS) and a Physical Uplink Shared Channel (PUSCH) (with up to four layers). With the increased number of DMRS ports in NRRel-18, there is an issue of how to allocate the PT-RS subcarriers when the PT-RS port is associated with one of the new DMRS ports in NRRel-18. Another issue is how to allocate the PT-RS to PDSCH or PUSCH power ratio per layer per resource element (RE) when the PT-RS can be associated to a PDSCH with more than six layers or DMRS ports or to a PUSCH with up to eight layers (transmitted through up to eight antenna ports).

[0093] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges. Some embodiments of the present disclosure provide a method for allocating subcarrier offsets for PT-RS ports associated to new NR Rel-18 DMRS ports, wherein existing rows in Table 7.4.1.2.2-1 of 3GPP TS 38.211 for downlink (DL) (reproduced herein as Table 1) and Table 6.4.1.2.2.1-1 of 3GPP TS 38.211 for uplink (UL) (reproduced herein as Table 2) are reused for Rel-18 DMRS ports with the same port index, while new rows are added for the remaining Rel-18 DMRS ports. For a given value of the Radio Resource Control (RRC) parameter "resourceElementOffset", different subcarrier offsets are assigned to PT-RS associated with different DMRS ports.

[0094] Some embodiments currently disclosed provide a method for allocating a PT-RS to PDSCH power ratio per RE per layer for a PDSCH having 7 and 8 layers, and for allocating a PT-RS to PUSCH power ratio per RE per layer for a PUSCH having more than four transmit (Tx) antenna ports and up to eight layers.

[0095] According to some embodiments of the present disclosure, when both PT-RS and Rel-18 DMRS ports 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.

[0096] According to some embodiments of the present disclosure, a method for allocating a subcarrier offset for a PT-RS port in each resource block (RB) allocated for the PT-RS port is provided, the method comprising: Define tables for DL ​​(e.g. Figure 2E ) and tables for UL (e.g. Figure 2F ), where each row is associated with the DMRS port associated with the PT-RS For a given associated DMRS port (type 1 or type 2) and "resourceElementOffset" The higher layer configuration of the value may determine the PT-RS subcarrier offset from one of the tables UE capability: In case of Type 1 DMRS, support for PTRS with isolated RBs (e.g. Figure 3A )

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

[0098] According to some embodiments of the present disclosure, a method for determining a PT-RS to PDSCH or PUSCH power ratio per RE per layer is provided, the method comprising: ·according to Figure 4A-1 The table shown in defines the PT-RS to PDSCH power ratio per RE per layer for PDSCH scheduled via 7 layers and 8 layers. • For partially coherent codebooks, the PT-RS to PUSCH power ratio per RE per layer may be PT-RS port specific or may be common for all PT-RS ports. o In the PT-RS port specific case, for each PT-RS port, the ratio is determined by the number of scheduled PUSCH layers associated to the PT-RS port and the total number of scheduled PT-RS ports associated to PUSCH (see Figure 4C-1 ). In case of PT-RS port sharing, the ratio may be determined 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 (see Figure 4C-2 、 4C-4 , 4C-5). For a fully coherent codebook, the PT-RS to PUSCH power ratio per RE per layer 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 RE per layer is determined by the number of scheduled PTs (see Figure 4A-4 ).

[0099] According to some embodiments of the present disclosure, communication systems and devices suitable for performing one or a combination of these steps are also provided.

[0100] Certain embodiments may provide one or more of the following technical advantages: The method enables phase tracking with PT-RS for PDSCH or PUSCH with up to eight layers by allocating appropriate subcarrier offsets and PT-RS to PDSCH or PUSCH power ratios in those scenarios.

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

[0102] When the number of DMRS ports is increased by applying a frequency domain orthogonal cover code (FD-OCC) code of length 4 in each legacy Rel-15 DMRS code division multiplexing (CDM) group and the DMRS ports are divided according to Figure 2C and Figure 2D , 8, 9, 10, 11}, and the associated twelve single-symbol type 2 DMRS ports are ports {0, 1, 2, 3, 4, 5, 12, 13, 14, 15, 16, 17} in the uplink (UL). Similarly, the associated single-symbol type 1 DMRS ports in the downlink (DL) are ports 1000 + {0, 1, 2, 3, 8, 9, 10, 11}, and the associated type 2 DMRS ports are ports 1000 + {0, 1, 2, 3, 4, 5, 12, 13, 14, 15, 16, 17}. These DMRS port indices are used as examples in the following discussion. Other ways of indexing DMRS ports are also possible. PT-RS subcarrier offset

[0103] Assume that the ULPT-RS port can be associated with eight type 1 DMRS ports of PUSCH One of {0, 1, 2, 3, 8, 9, 10, 11}, and the DLPT-RS port can be associated to one of the eight type 1 DMRS ports 1000+{0, 1, 2, 3, 8, 9, 10, 11} of PDSCH.

[0104] In one embodiment, the ULPT-RS port can be associated with one of the twelve type-2 DMRS ports {0, 1, 2, 3, 4, 5, 12, 13, 14, 15, 16, 17) of the PUSCH, and the DLPT-RS port can be associated with one of the twelve type-2 DMRS ports 1000+{0, 1, 2, 3, 4, 5, 12, 13, 14, 15, 16, 17} of the PDSCH.

[0105] In one embodiment, the subcarrier offset For PT-RS associated with DMRS port, Figure 2E Medium (for DLPT-RS) and Figure 2F is allocated as shown in (for ULPT-RS), where Figure 2E The rows with p=1000 to p=1005 and the rows with arrive The rows of the legacy tables (i.e., Table 7.4.1.2.2-1 in 3GPP TS 38.211 for DL ​​and Table 6.4.1.2.2.1-1 in 3GPP TS 38.211 for UL) are reused. In another embodiment, a subset of the columns may be included in the specification. For example, for Type 2 DMRS, only offset=00 may be included.

[0106] In one embodiment, a new PTRS subcarrier offset table (one for DL ​​and / or one for UL) is introduced in NR for Rel-18 DMRS, where some legacy entries (i.e. Figure 2E The lines for ports 1000 to 1005 and Figure 2F The rows for ports 0 to 5 in are also updated, i.e., Figure 2E and Figure 2F The table shown in FIG for DMRS antenna ports 1000-1005 ( Figure 2E ) or 0-5( Figure 2F ) can be compared to some items of Figure 2E and Figure 2F The values ​​shown in are changed.

[0107] Figure 2E and Figure 2F The allocation in ensures that for the same resourceElementOffset configuration, i.e. one of the four configurations offset00, offset01, offset10, offset11, the PT-RS ports associated to different DMRS ports are allocated in different subcarriers. This will prevent conflicts 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. In the case of type 1 DMRS, all eight DMRS ports will be allocated (i.e. ports 1000 to 1003 and 1008 to 10011 for PDSCH, and ports 0 to 3 and 8 to 11 for PUSCH). If PT-RS is also configured for all UEs and all PT-RS ports happen to be allocated in the same RB, the PT-RS ports cannot overlap and must be allocated in different REs (i.e. with different subcarrier offsets). By Figure 2E and Figure 2F In the subcarrier offset allocation, PT-RS associated with different DMRS ports are always allocated to different subcarriers.

[0108] Isolated RB of Type 1 DMRS:

[0109] When Rel-18 DM-RS enhancement configuration type 1 is configured, the number of REs per CDM group on the scheduled bandwidth may not be an integer multiple of the length of the FD-OCC code (i.e., for configuration type 1, there are 6 REs per CDM group per RB, and the length of the FD-OCC code is 4). This is called an "orphan RE". For example, this occurs when an odd number of consecutive RBs are scheduled or when the scheduled PDSCH is scheduled with an odd number of PRB offsets from point A (CRB0). One possible solution is to apply scheduling restrictions such that the number of consecutively scheduled PRBs and the PRB offset of the scheduled PDSCH from CRB0 are even. However, in Rel-18, there is a UE capability for cases where such scheduling restrictions do not have 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 an odd number. However, how DMRS channel estimation is implemented in this case depends on the UE implementation. In one embodiment, for downlink PT-RS, when the UE indicates this capability, only subcarrier offsets in the range of 0-7 are allowed, and the UE can be scheduled with an odd number of consecutive PRBs. This means that reference Figure 2E and Figure 2F The following combination: For offset00, Figure 2E All combinations with ports 1000-1003 and 1008-1011 are allowed; For offset01, Figure 2E The combination with ports 1000-1003, 1008 and 1010 is allowed; For offset10, Figure 2E The combination with ports 1000, 1002, 1009 and 1011 is allowed; For offset11, Figure 2E The combination with ports 1008-1011 is allowed; For offset00, Figure 2F All combinations with ports 0-3 and 8-11 are allowed; For offset01, Figure 2F Combinations with ports 0-3, 8, and 10 are allowed in; For offset10, Figure 2F Combinations with ports 0, 2, 9, and 11 are allowed in; For offset11, Figure 2F Combinations with ports 8-11 are allowed.

[0110] In one embodiment, when the number of consecutively scheduled PRBs in the downlink is an odd number or the PRB offset of the scheduled PDSCH from CRB0 is an odd number, and when an disallowed 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 a variation of this embodiment, when the disallowed 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) in each set of consecutively scheduled PRBs and assumes that the PT-RS is present in the remaining PRBs. In another variation of this embodiment, when the disallowed 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) in each set of consecutively scheduled PRBs and assumes that the PT-RS is present in the remaining PRBs. In yet another variation of this embodiment, the UE assumes that the PT-RS is not present in the RB associated with the orphan RE.

[0111] In another embodiment, when the number of consecutively scheduled PRBs in the uplink or the PRB offset of the scheduled PUSCH from CRB0 is an odd number, and when an unallowed 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 a variation of this embodiment, when the unallowed 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) in each set of consecutively scheduled PRBs, but instead transmits PT-RS in the remaining PRBs. In another variation of this embodiment, when the unallowed 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) in each set of consecutively scheduled PRBs, but instead transmits PT-RS in the remaining PRBs.

[0112] Figure 3A Shown with 'offset01' and DMRS antenna port An example corresponding to the allowed combinations of , in this case the subcarrier offset is

[0113] In one embodiment, the parameter "resourceElementOffset" defined in the PTRS-DownlinkConfig information element and the PTRS-UplinkConfig information element in 3GPP TS 38.331 for Rel-15 DMRS is also reused for Rel-18 extended DMRS. One benefit of this solution is that if a UE is configured with both Rel-15 and Rel-18 DMRS, the amount of radio resource control (RRC) signaling is reduced compared to introducing new dedicated parameters for Rel-18 DMRS PTRS offset allocation.

[0114] In one embodiment, Figure 3B and Figure 3C As shown in , a new dedicated parameter is introduced in the PTRS-DownlinkConfig information element and / or the PTRS-UplinkConfig information element in 3GPP TS 38.331, here called "resourceElementOffset-Rel18". One benefit of this solution is that different PTRS mappings can be used for Rel-15 and Rel-18 DMRS (e.g., offset00 for Rel-15 DMRS and offset10 for Rel-18 DMRS), which may be useful, for example, if dynamic switching between Rel-15 and Rel-18 DMRS is supported, because the NR base station (gNB) can dynamically update the PTRS frequency allocation by switching between Rel-15 and Rel-18 DMRS (this may be useful, for example, when the network notices poor PTRS performance in the UL, which may be due to conflicting PTRS from another UE in the same or different cell, and the network can then test switching PTRS allocation by switching from Rel-15 DMRS to Rel-18 DMRS or vice versa). In some embodiments, the frequency density of PTRS can 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 information element and / or the PTRS-UplinkConfig information element in TS 38.331. This is beneficial if dynamic switching between Rel-15 and Rel-18 DMRS is supported, where the gNB can dynamically update the PTRS frequency density by switching between Rel-15 and Rel-18 DMRS.

[0115] In some other embodiments, the time density of PTRS configured for Rel-15 and Rel-18 DMRS may be different. 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 information element and / or the PTRS-UplinkConfig information element in TS 38.331. This is beneficial if dynamic switching between Rel-15 and Rel-18 DMRS is supported, where the gNB can dynamically update the PTRS time density by switching between Rel-15 and Rel-18 DMRS. PT-RS power boost

[0116] In NR Releases 15 to 17, the number of PDSCH layers supported when 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 the new Rel-18 DMRS ports, up to eight layers can be supported for PDSCH or PUSCH when PT-RS is configured. Depending on the number of PDSCH or PUSCH layers associated with a PT-RS port, the transmit power of the PT-RS port can be increased relative to the corresponding PDSCH or PUSCH transmit power per layer per RE.

[0117] In one embodiment, Figure 4A-1 The PT-RS and PDSCH transmission power ratio per RE per layer is given in PTRS , where for layers one to six, the traditional ratios can be reused; while for layers seven and eight, the associated PT-RS ports can be boosted by 8.45dB (i.e., 10log10(7)) and 9.03dB (i.e., 10log10(8), note that 9.03 may be rounded down to 9 in the specification). Note that the same ratios as in Figure 4A-1 The table in FIG4 indicates epre-Ratio=0. Different epre-Ratio values ​​are used to indicate seven and eight layers.

[0118] For PUSCH transmission with up to 8 layers and up to 8 Tx antenna ports, the Tx antenna ports can be fully coherent, partially coherent, or non-coherent. The corresponding fully coherent, partially coherent, or non-coherent codebooks can be designed accordingly. Each PUSCH layer is associated with a DMRS port. A PT-RS port can be associated with one or more PUSCH layers or DMRS ports.

[0119] In the case of a fully coherent codebook, the precoder w=[w(1),…,w(N Tx )] T The PUSCH layer is transmitted on all antenna ports, 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. PUSCH layers are scheduled, and each PUSCH layer is used The total transmission power (i.e. If PT-RS is configured, it is associated to one of the DMRS ports and is precoded in the same way as the associated DMRS port (or associated PUSCH layer). The PT-RS to PUSCH power ratio per RE per layer is given by That is, the PT-RS port can use all available power across all antenna ports, while each PUSCH layer uses only a small portion of the total power. Figure 4A-2 , where "xx" represents a code point in the higher layer parameter "UL-PTRS-power", indicating a row in the table. When the code point "xx" is configured for "UL-PTRS-power", the UE Figure 4A-2 The PT-RS transmission power is determined according to the table shown in .

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

[0121] In the case of partially coherent codebooks, N Tx The antenna ports may be divided into multiple antenna port groups, wherein the antenna ports within each port group are coherent and the antenna ports in different antenna port groups are incoherent. Each port group may be associated with a certain PT-RS port. Figure 4B-1 Show NTx =8 and 2 antenna port groups, where antenna ports 1 to 4 form a first port group and antenna ports 5 to 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 transmitting a PUSCH layer in port group 1, the precoder takes the form w = [w(1), ..., w(4), 0, ..., 0] T , where for i = 1, ..., 4, w(i) ≠ 0 and for i = 5, ..., 8, w(i) = 0. Similarly, when the PUSCH layer is transmitted in port group 2, the corresponding precoder takes the form of 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 PUSCH layers can be transmitted, and each layer is allocated 1 / r of the total transmit power available in the antenna port group, i.e., Where r is the number of layers in the port group. It is assumed here 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 requires a maximum of two PT-RS ports.

[0122] The above can be expanded to 4 antenna groups, as shown in the example 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 in the form of w = [w(1), ..., w(2), 0, ..., 0) T , where for i = 1, 2, w(i) ≠ 0 and for i = 3, ..., 8, w(i) = 0. Similarly, when the PUSCH layer is transmitted in port group 2, the corresponding precoder adopts the form of 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 PUSCH layers can be scheduled or transmitted, and each layer is allocated 1 / r of the total transmit power in the antenna port group, i.e., Where r is the number of layers scheduled in the port group. It is assumed here 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 requires a maximum of four PT-RS ports.

[0123] PT-RS port specific PT-RS power boost:

[0124] In one embodiment, for each PT-RS port, the PT-RS to PUSCH transmit power ratio per RE per layer is determined by the associated number of PUSCH layers scheduled in the same port group, i.e., in is associated with PTRS port k (k=0,1,…,Q p -1) in the antenna port group, and Q p is the total number of scheduled PT-RS ports across antenna port groups. For different PT-RS ports, Can be the same or different, depending on whether the same number of PUSCH layers or a different number of PUSCH layers are scheduled in the corresponding antenna port groups. For example, assuming that in the previous example with 8 antenna ports, PT-RS port 0 is associated to antenna port group 1, and PT-RS port 1 is associated to antenna port group 2, if 2 layers are scheduled in port group 1 and 3 layers are scheduled in port group 2, then Q p =2, and for PT-RS port 0, And for PT-RS port 1, In another example with 4 antenna port groups, assuming that PT-RS ports {0, 1, 2, 3} are associated to antenna port groups {1, 2, 3, 4}, then if 2 layers are scheduled in port group 1 and 1 layer is scheduled in each of port groups {2, 3, 4}, then Q p =4, and for PT-RS port 0, And for PT-RS ports {1,2,3},

[0125] Usually, for N ant,groups antenna groups and Q p (Q p ≤N ant,groups ) PT-RS ports (associated with scheduled PUSCH), the PT-RS to PDSCH transmit power ratio per RE per layer of the PT-RS port is determined by the number of scheduled PUSCH layers associated with the PT-RS ports in the same antenna port group, i.e. This is Figure 4C-1 Note that for 8 Tx antennas with 4 port groups (each port group has two antenna ports),

[0126] There is another case with mixed partially coherent and non-coherent port groups, where in the first port group(s), the PUSCH layer is transmitted on only a single antenna port, while in the second port group(s), the PUSCH layer is transmitted on all antenna ports of one port group. In one embodiment, for the PT-RS ports associated to the first port group(s), the PT-RS to PUSCH transmit power ratio per RE per layer is calculated based on Figure 4A-4 For the PT-RS port associated with the second port group (one or more), the PT-RS and PUSCH transmission power ratio per RE per layer is determined according to Figure 4A-2 For example, for 8 antenna ports with four antenna port groups and 5 PUSCH layers as Figure 4C-2 w1 = [w1(1), 0,,…, 0] T w2=[0 w2(2),0,…,0] T In this case, for PT-RS port 0, the PT-RS and PUSCH transmission power ratio per RE per layer is determined according to, Right now, For PT-RS ports 1 to 3, the PT-RS and PUSCH transmission power ratios per RE per layer are calculated based on Figure 4A-2 To determine, that is

[0127] Note that the PT-RS to PUSCH transmit power ratio per RE per layer for the PT-RS port discussed above represents the maximum PT-RS to PUSCH transmit power ratio per RE per layer that can be achieved. In some cases, the PT-RS to PUSCH transmit power ratio per RE per layer can be limited to a certain value Y (dB). For example, the maximum PT-RS to PUSCH transmit power ratio per layer can be limited to Y = 6dB. In this case, if Figure 4A-1 、 4A-2 , 4A-4 and 4C-1 are greater than Y, they will be set to YdB. Alternatively, different rows in the tables in 4A-1, 4A-2, 4A-4 and 4C-1 can be used for the purpose. Figure 4C-3 An example is shown in , where a newline "yy" is used.

[0128] Common PT-RS power boosts:

[0129] In some cases, there is a need to perform the same power boost on all PT-RS ports. In the following embodiments, it is assumed that the same PT-RS to PUSCH EPRE power ratio per layer per RE is determined for all scheduled PT-RS ports.

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

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

[0132] Figure 4C-4 An example of a PT-RS to PUSCH EPRE power ratio table for 2 antenna groups is shown, 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 = 1, and when some PUSCH layers are transmitted in one antenna group and other layers are transmitted in another antenna group, Q p =2. For up to 5 PUSCH layers, there is the possibility that one layer is scheduled / transmitted in the first antenna group, while the remaining layers are scheduled / transmitted in the second antenna group. For the PT-RS in the first antenna group, it will have the same power per layer per RE as the PUSCH in the same antenna group (if power is not borrowed from unused / blank REs associated with the PT-RS ports in the second antenna group). When power is borrowed from unused / blank REs associated with the PT-RS ports in the second antenna group, the PT-RS to PUSCH EPRE power ratio is 3dB or (3Q p -3). For a PUSCH with 6 layers, at least two PUSCH layers need to be scheduled / transmitted in each of the two antenna groups. Without borrowing power from unused / blank REs associated with the PT-RS port in the other antenna group, the PT-RS to PUSCH EPRE power ratio is at least 3dB. With power borrowing, the PT-RS to PUSCH EPRE power ratio is at least 6dB or 3Q. p. For 7 and 8 PUSCH layers, at least three and four PUSCH layers, respectively, need to be scheduled / transmitted in each of the two antenna groups. With power borrowing, the PT-RS to PUSCH EPRE power ratio is at least 7.78dB (i.e., 10log10(6)) for 7 layers and at least 9.03dB (i.e., 10log10(8)) for 8 layers. In the row with "UL-PTRS-power=00", it limits the maximum PT-RS power boost to 6dB.

[0133] It may be possible that not all possible rank combinations are allowed for an 8TX UE with 2 antenna groups in order to save PMI overhead. For example, the number of layers in one antenna group cannot differ by more than one from the number of layers in the other antenna group. In this case, one or more of the following rank combinations will not be supported: 4+1 (i.e., 4 layers for the first antenna group and 1 layer for the second antenna group), 3+1, etc., and the PT-RS to PUSCH power ratio will be determined by the PT-RS port associated with the antenna group with the smaller number of assigned PUSCH layers, i.e. For example, for a total of 3 PUSCH layers, if one layer is in antenna group 1 and 2 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. By this method, the PT-RS to PUSCH EPRE power ratio for different numbers of PUSCH layers can also be determined. Figure 4C-3 An example is shown in the row with "UL PTRS-power=01".

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

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

[0136] Note that the quantities in all tables are approximate and may be rounded up or down in the 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 contained in the remaining rows / columns of the table).

[0137] Figure 5A A method, performed in a wireless communication system, is provided for allocating a subcarrier offset for a phase tracking reference signal (PT-RS) port in each resource block (RB) allocated for the PT-RS port. When both PT-RS and Rel 18 DMRS ports are allocated 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. The method includes one or more of the following steps: (Step 500A) For a given associated DMRS port and higher-layer configuration of resource offset parameters, determine the PT-RS subcarrier offset from an uplink (UL) table or a downlink (DL) table, where each table row is associated with a DMRS port associated with that PT-RS; and (Step 502-A) in the case of Type 1 DMRS, support the PTRS for the orphan RB by the user equipment. These steps may be performed in any combination and in any order.

[0138] Figure 5B5. The present invention relates to a method for allocating a PT-RS subcarrier offset for each RB allocated for a PT-RS port by a UE or a network node (e.g., a base station, such as a gNB) according to an embodiment of the present disclosure, wherein both PT-RS and DMRS ports are configured for the UE. Here, the term "node" is used to refer to a device that performs the method, which can be a UE or a network node. As shown in the figure, for each RB of one or more RBs allocated for a PT-RS port configured for the UE, the node determines the PT-RS subcarrier offset for the PT-RS port from a table (e.g., a 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, wherein the PT-RS port is associated with a PDSCH or PUSCH having more than 6 spatial layers, and the DMRS type is an enhanced DMRS type that supports at least 8 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, wherein eight of the plurality of DMRS ports are associated with a first DMRS configuration type and twelve of the plurality of DMRS ports are associated with a second DMRS configuration type. In addition, each row of the table is associated with one of the plurality of DMRS ports and defines a different PT-RS subcarrier offset for the PT-RS port associated with the one of the plurality of DMRS ports for different resource element offset parameter values ​​of at least one of the first DMRS configuration type and the second DMRS configuration type. The node transmits or receives a PT-RS on the PT-RS port in each of the one or more RBs according to the determined PT-RS subcarrier offset (step 502-B). In one embodiment, the table is an uplink table, such as Figure 2F In this case, 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 Figure 2E In this case, the PT-RS is transmitted by the network node on the downlink and received by the UE. In addition, the node may perform one or more actions related to the orphaned RB of the Type 1 DMRS (step 504-B). The details of such actions have been described above and are therefore not repeated here.

[0139] Figure 5CA method in a wireless communication system is shown for determining a power ratio of a phase tracking reference signal PT-RS to a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH per resource element RE per layer, wherein both PT-RS and Rel18 DMRS ports are configured for a UE and the PDSCH or PUSCH is scheduled with up to 8 layers. The method includes one or more of the following steps: determining (500-C) a PT-RS to PDSCH power ratio per RE per layer for PDSCH scheduled with 7 layers and 8 layers according to a table; determining (502-C) a PT-RS to PUSCH power ratio per RE per layer specific to a PT-RS port or common to all PT-RS ports for a partially coherent codebook; in the case of PT-RS port specificity, determining, for each PT-RS port, the PT-RS to PUSCH power ratio by the number of scheduled PUSCH layers associated with the PT-RS port and the number of scheduled PT-RS configured for the PUSCH. The ratio is determined based on the total number of S ports; in the case of PT-RS port sharing, the ratio is determined 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, the PT-RS to PUSCH power ratio per RE per layer is determined (504-C) by the number of scheduled PUSCH layers; and / or for a non-coherent codebook, the PT-RS to PUSCH power ratio per RE per layer is determined (506-C) by the configured PT-RS ports for PUSCH. These steps can be performed in any combination and in any order.

[0140] Figure 5D 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 is illustrated. The transmitting node determines a PT-RS to PxSCH power ratio per RE per spatial layer for a PT-RS port associated with a scheduled PxSCH transmission for the UE, where the PxSCH transmission has up to 8 spatial layers (step 500-D). Note that as used herein, "PxSCH" is a general term referring to PDSCH or PUSCH. The transmitting node determines a PT-RS to PxSCH power ratio per RE per spatial layer for the PT-RS port associated with the scheduled PxSCH transmission (according to any of the embodiments described above for doing so). The transmitting node transmits the scheduled PxSCH transmission (step 502-D), and together with the scheduled PxSCH transmission, also transmits the PT-RS on the PT-RS port in each RE allocated to the PT-RS port with a transmission power according to the determined PT-RS to PxSCH power ratio per RE per spatial layer (step 504-D).

[0141] Figure 6 An example of a communication system 600 is shown in accordance with some embodiments.

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

[0143] Example wireless communications over a wireless connection include transmitting 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. Additionally, in various embodiments, the 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). The communication system 600 may include, and / or be connected to via an interface, any type of communication network, telecommunications network, data network, cellular network, radio network, and / or other similar types of systems.

[0144] The UE 612 may be any of a variety of communication devices, including wireless devices that are arranged, configured, and / or operable to communicate wirelessly with the network node 610 and other communication devices. Similarly, the network node 610 is arranged, capable, configured, and / or operable to communicate directly or indirectly with the UE 612 and / or with other network nodes or devices in the telecommunications network 602 to enable and / or provide network access (such as wireless network access) and / or perform other functions (such as management in the telecommunications network 602).

[0145] In the depicted example, core network 606 connects network node 610 to one or more hosts, such as host 616. These connections can be direct or indirect (via one or more intermediate networks or devices). In other examples, the network node can be directly coupled to the host. Core network 606 includes one or more core network nodes (e.g., core network node 608), which are constructed using hardware and software components. The features of these components can be substantially similar to those described for the UE, network node, and / or host, so that the description is generally applicable to the corresponding components of core network node 608. Example core network nodes include the functionality of one or more of the following: 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 dehiding function (SIDF), a unified data management (UDM), a security edge protection proxy (SEPP), a network exposure function (NEF), and / or a user plane function (UPF).

[0146] The host 616 may be under the ownership or control of, and may be operated by or on behalf of, a service provider other than the operator or provider of the access network 604 and / or telecommunications network 602. The host 616 may host various applications to provide one or more services, examples of which include live and pre-recorded audio / video content, data collection services (such as retrieving and compiling data about various environmental conditions detected by multiple UEs), analytics functionality, social media, functionality for controlling or otherwise interacting with remote devices, functionality for an alarm and monitoring center, or any other such functionality performed by a server.

[0147] As a whole, Figure 6The communication system 600 can enable connectivity between UEs, network nodes, and hosts. In that sense, the communication system 600 can be configured to operate according to predefined rules or procedures, such as a specific 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) standards or any applicable future generation standards (e.g., sixth generation (6G)); Wireless Local Area Network (WLAN) standards such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other suitable wireless communication standards such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox.

[0148] In some examples, telecommunication network 602 is a cellular network that implements 3GPP standardized features. Thus, telecommunication network 602 can support network slicing to provide different logical networks to different devices connected to telecommunication network 602. For example, telecommunication network 602 can provide ultra-reliable low-latency communication (URLLC) services to some UEs while providing enhanced mobile broadband (eMBB) services to other UEs, and / or provide massive machine type communication (mMTC) / massive Internet of Things (IoT) services to yet other UEs.

[0149] In some examples, the UE 612 is configured to transmit and / or receive information without direct human interaction. For example, the UE can be designed to transmit information to the access network 604 according to a predetermined schedule when triggered by an internal or external event, or in response to a request from the access network 604. In addition, the UE can be configured to operate in a single radio access technology (RAT) or multiple radio access technologies (RAT) or multi-standard mode. For example, the UE can operate with any one or a combination of Wi-Fi, New Radio (NR), and LTE, i.e., be configured for multi-radio dual connectivity (MR-DC), such as evolved UMTS terrestrial RAN (E-UTRAN) NR-dual connectivity (EN-DC).

[0150] In this example, hub 614 communicates with access network 604 to facilitate indirect communication between one or more UEs (e.g., UE 612C and / or 612D) and a network node (e.g., network node 610B). In some examples, hub 614 can be, for example, a controller, a router, a content source, and an analyzer, or any other communication device described herein with respect to a UE. For example, hub 614 can be a broadband router that enables UE access to core network 606. As another example, hub 614 can be a controller that sends commands or instructions to one or more actuators in the UE. The commands or instructions can be received from the UE, from the network node 610, or through executable code, scripts, processes, or other instructions in hub 614. As another example, hub 614 can be a data collector that acts as a temporary storage device for UE data and, in some embodiments, can perform analysis or other processing on the data. As another example, hub 614 can be a content source. For example, for a UE that is a virtual reality (VR) headset, display, speaker, or other media delivery device, the hub 614 can retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, and then the hub 614 provides these contents directly to the UE 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 UE, especially when one or more of the UEs are low-energy IoT devices.

[0151] The hub 614 may have a constant / persistent or intermittent connection to the network node 610B. The hub 614 may also allow different communication schemes and / or scheduling between the hub 614 and the UEs (e.g., UE 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. In addition, the hub 614 may be configured to connect to a machine-to-machine (M2M) service provider through the access network 604 and / or to another UE via a direct connection. In some cases, a UE may establish a wireless connection with the network node 610 while still being connected via the hub 614 via a wired or wireless connection. In some embodiments, the hub 614 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 610B. In other embodiments, hub 614 may be a non-dedicated hub—ie, a device operable to route communications between UEs and network node 610B, but otherwise capable of operating as a communications start and / or end point for certain data channels.

[0152] Figure 7UE 700 according to some embodiments is shown. As used herein, UE refers to a device capable of, configured, arranged and / or operable to wirelessly communicate with a network node and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cellular phones, voice over Internet Protocol (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptop computers, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), vehicle mounted or vehicle embedded / integrated wireless devices, etc. Other examples include any UE identified by 3GPP, including narrowband Internet of Things (NB-IoT) UEs, machine type communication (MTC) UEs and / or enhanced MTC (eMTC) UEs.

[0153] The UE may support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, dedicated short-range communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user owning and / or operating an associated device. Instead, the UE may represent a device that is intended to be sold to or operated by a human user, but may not be, or may not initially be, associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, the UE may represent a device that is not intended to be sold to or operated by an end user, but may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0154] UE 700 includes processing circuitry 702 operatively coupled to input / output interface 706, power source 708, memory 710, communication interface 712, and / or any other components or any combination thereof via bus 704. A particular UE may utilize Figure 7 All or a subset of the components shown in . The level of integration between components may vary from one UE to another UE. In addition, a particular UE may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0155] 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 as a machine-readable computer program in the memory 710. 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 along with appropriate firmware; one or more stored computer programs, a general-purpose processor (such as a microprocessor or a digital signal processor (DSP)) along with appropriate software; or any combination of the above. For example, the processing circuit 702 may include multiple central processing units (CPUs).

[0156] In this example, the input / output interface 706 can 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, a transmitter, a smart card, another output device, or any combination thereof. An input device can 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 web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, and the like. A presence-sensitive display can include a capacitive or resistive touch sensor to sense input from the user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. The output device can use the same type of interface port as the input device. For example, a Universal Serial Bus (USB) port can be used to provide both the input device and the output device.

[0157] In some embodiments, the power source 708 may be configured as a battery or battery pack. Other types of power sources may be used, such as an external power source (e.g., a power outlet), a photovoltaic device, or a power unit. The power source 708 may also include a power circuit for delivering power from the power source 708 itself and / or an external power source to various parts of the UE 700 via an input circuit or an interface such as a power cable. For example, the delivered power may be used to charge the power source 708. The power circuit may perform any formatting, conversion, or other modification on the power from the power source 708 so that the power is suitable for the corresponding components of the UE 700 to which the power is supplied.

[0158] The memory 710 may be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically EPROM (EEPROM), a magnetic disk, an optical disk, a hard disk, a removable cartridge, a 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 operating systems or a combination of operating systems for use by the UE 700.

[0159] The memory 710 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical drive, an internal hard drive, a Blu-ray disc drive, a holographic digital data storage (HDDS) optical drive, an external micro dual in-line memory module (DIMM), synchronous dynamic RAM (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) including one or more subscriber identity modules (SIMs), such as a universal SIM (USIM) and / or an Internet Protocol Multimedia Services identity module (ISIM)), other memories, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC, commonly referred to as a "SIM card." The memory 710 may allow the UE 700 to access instructions, applications, and the like stored on a transient or non-transitory storage medium to offload data or upload data. An article of manufacture, such as an article of manufacture utilizing a communication system, may be tangibly embodied as or in memory 710 , which may be or may include a device-readable storage medium.

[0160] The processing circuit 702 can be configured to communicate with an access network or other network using a communication interface 712. The communication interface 712 may include 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 for communication, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an 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.). In addition, the transmitter 718 and the receiver 720 may be coupled to one or more antennas (e.g., antenna 722) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0161] In the illustrated embodiment, the communication functionality of the communication interface 712 may include cellular communication, Wi-Fi 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 functionality, or any combination thereof. Communication may be implemented according to 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), fast user datagram protocol Internet connection (QUIC), hypertext transfer protocol (HTTP), etc.

[0162] Regardless of the type of sensor, the UE can provide an output of the data captured by its sensor through its communication interface 712 or via a wireless connection to a network node. The data captured by the UE's sensor can be delivered to the network node via another UE via a wireless connection. The output can be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load of reports from several sensors), in response to a trigger event (e.g., sending an alarm when moisture is detected), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0163] As another example, a UE includes an actuator, motor, or switch associated with a communication 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 can change. For example, the UE can include a motor that adjusts the control surfaces or rotors of a drone in flight based on the received input, or controls a robotic arm performing a medical procedure based on the received input.

[0164] A UE, when in the form of an IoT device, may be a device for use in one or more application areas including, but not limited to, urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices are devices that are or are embedded in connected refrigerators or freezers, televisions, connected lighting devices, electricity meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / humidity sensors, electric door locks, connected doorbells, air conditioning systems such as heat pumps, autonomous vehicles, surveillance systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smart watches, fitness trackers, head-mounted displays for augmented reality (AR) or VR, wearable devices for tactile or sensory enhancement, sprinklers, animal or item tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any type of medical device, such as a heart rate monitor or a teleoperated surgical robot. In addition to the above, Figure 7 In addition to the other components described for UE 700 shown in FIG, a UE in the form of an IoT device may further include circuitry and / or software depending on the intended application of the IoT device.

[0165] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another UE and / or a network node. In this case, the UE may be an M2M device, which in the 3GPP context may be referred to as an MTC device. As a specific example, a 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 device capable of monitoring and / or reporting its operating status or other functions associated with its operation.

[0166] In practice, any number of UEs can be used together for a single use case. For example, a first UE can be or be integrated into a drone and provide the drone's speed information (obtained via a speed sensor) to a second UE, which is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE can adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UE can also include more than one of the above functionalities. For example, a UE can include a sensor and an actuator and handle data communication for both the speed sensor and the actuator.

[0167] Figure 8 A network node 800 according to some embodiments is shown. As used herein, a network node refers to a device capable of, configured, arranged, and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, APs (e.g., radio APs), base stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).

[0168] BSs can be classified based on the amount of coverage they provide (or, in other words, their transmit power level), and therefore, depending on the amount of coverage provided, can be referred to as femto BSs, pico BSs, micro BSs, or macro BSs. A BS can be a relay node or a relay donor node that controls a relay. A network node can also include one or more (or all) parts of a distributed radio BS, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such an RRU can be integrated with an antenna or be an antenna-integrated radio device without being integrated with an antenna. Parts of a distributed radio BS can also be referred to as nodes in a distributed antenna system (DAS).

[0169] Other examples of network nodes include multi-transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as an 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 transmission 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 minimization of drive tests (MDT).

[0170] Network node 800 includes processing circuitry 802, memory 804, a communication interface 806, and a power source 808. Network node 800 may be comprised of multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own corresponding components. In certain instances where network node 800 includes 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, in some instances, each unique Node B and RNC pair may be considered a single, separate network node. In some embodiments, network node 800 may be configured to support multiple RATs. In such embodiments, some components may be replicated (e.g., separate memory 804 for different RATs), and some components may be reused (e.g., the same antenna 810 may be shared by different RATs). The network node 800 may also include multiple sets of the various illustrated components for different wireless technologies, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-Wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies, integrated into the network node 800. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node 800.

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

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

[0173] The memory 804 may include any form of volatile or non-volatile computer-readable memory, including but not limited to permanent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (e.g., a hard disk), removable storage media (e.g., a flash drive, a compact disk (CD), or a digital video disk (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 can be used by the processing circuit 802. The memory 804 may store any suitable instructions, data, or information, including computer programs, software, applications (including one or more of logic, rules, code, tables, etc.), and / or other instructions (capable of being executed by the processing circuit 802 and utilized by the network node 800). The memory 804 may be used to store any calculations performed by the processing circuit 802 and / or any data received via the communication interface 806. In some embodiments, the processing circuit 802 and the memory 804 are integrated.

[0174] The communication interface 806 is used for wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As shown, the communication interface 806 includes (one or more) ports / (one or more) terminals 816, for example, to send data to and receive data from the network via a wired connection. The communication interface 806 also includes a radio front-end circuit 818, which can be coupled to the antenna 810 or, in some embodiments, is part of the antenna 810. The radio front-end circuit 818 includes a filter 820 and an amplifier 822. The radio front-end circuit 818 can be connected to the antenna 810 and the processing circuit 802. The radio front-end circuit 818 can be configured to condition the signals transmitted between the antenna 810 and the processing circuit 802. The radio front-end circuit 818 can receive digital data to be transmitted to other network nodes or UEs via a wireless connection. The radio front-end circuit 818 can use a combination of the filter 820 and / or the amplifier 822 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal can then be transmitted via the antenna 810. Similarly, when receiving data, antenna 810 may collect radio signals, which are then converted into digital data by radio front-end circuitry 818. The digital data may be passed to processing circuitry 802. In other embodiments, communication interface 806 may include different components and / or different combinations of components.

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

[0176] Antenna 810 may include one or more antennas or antenna arrays configured to transmit 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 may be separate from network node 800 and may be connected to network node 800 via an interface or port.

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

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

[0179] An embodiment of the network node 800 may include Figure 8, which are used to provide certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, network node 800 may include a user interface device to allow information to be input into network node 800 and to allow information to be output from network node 800. This may allow a user to perform diagnostic, maintenance, repair, and other management functions for network node 800.

[0180] Figure 9 is a block diagram of a host 900 according to various aspects described herein, which may be Figure 6 As used herein, host 900 may be or include various combinations of hardware and / or software, including processing resources in a standalone server, blade server, cloud-enabled server, distributed server, virtual machine, container, or server farm. Host 900 may provide one or more services to one or more UEs.

[0181] Host 900 includes processing circuitry 902 operatively coupled to input / output interface 906, network interface 908, power source 910, and memory 912 via bus 904. Other components may be included in other embodiments. The features of these components may be substantially similar to those described with respect to previous figures (such as Figure 7 and Figure 8 ) so that its description is generally applicable to the corresponding components of the host 900.

[0182] Memory 912 may include one or more computer programs, including one or more host applications 914, and data 916, which may include user data, such as data generated by a UE for host 900 or data generated by host 900 for a UE. Embodiments of host 900 may utilize only a subset or all of the components shown. Host application 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, and g.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., mobile phones, desktop computers, wearable display systems, and heads-up display systems). Host application 914 may also provide user authentication and permission checks, and may periodically report health, routing, and content availability to a central node (e.g., a device in or at the edge of the core network). Thus, the host 900 can select and / or instruct the UE on different hosts for over-the-top (OTT) services. The host application 914 can support various protocols, such as HTTP Live Streaming (HLS), Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (DASH or MPEG-DASH), etc.

[0183] Figure 10 1000 is a block diagram illustrating a virtualized environment in which the functions implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of a device or apparatus, which may include a virtualized hardware platform, storage device, and networking resources. As used herein, virtualization can be applied to any apparatus described herein or its components, and relates to an implementation in which at least a portion of functionality is implemented as one or more virtual components. Some or all of the functions described herein can be implemented as virtual components performed by one or more virtual machines (VMs), which are implemented in one or more virtual environments 1000 hosted by one or more hardware nodes, which are hardware computing devices such as those operated as network nodes, UEs, core network nodes, or hosts. In addition, in embodiments where a virtual node does not require radio connectivity (e.g., a core network node or host), the node can be fully virtualized.

[0184] Applications 1002 (which may alternatively be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) run in virtualized environment 900 to implement some features, functions, and / or benefits of some embodiments disclosed herein.

[0185] The hardware 1004 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices as described herein, such as network interfaces, input / output interfaces, and the like. The software may be executed by the processing circuitry to instantiate one or more virtualization layers 1006 (also referred to as hypervisors or VM monitors (VMMs)), provide VMs 1008A and 1008B (one or more of which may be collectively referred to as VMs 1008), and / or perform any of the functions, features, and / or benefits described with respect to some embodiments described herein. The virtualization layer 1006 may present a virtual operating platform that appears to be networked hardware to the VMs 1008.

[0186] The VMs 1008 include virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and can be run by a corresponding virtualization layer 1006. Different embodiments of instances of virtual devices 1002 can be implemented on one or more of the VMs 1008, and the implementation can be performed in different ways. Virtualization of hardware is referred to in some contexts as network function virtualization (NFV). NFV can be used to consolidate many network device types onto industry-standard high-capacity server hardware, physical switches, and physical storage (which can be located in data centers as well as customer premises equipment).

[0187] In the context of NFV, VMs 1008 can be software implementations of physical machines that run programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1008 and the portion of the hardware 1004 on which it executes (whether dedicated to that VM and / or shared with other VMs 1008) forms a separate virtual network element. Still in the context of NFV, a virtual network function is responsible for handling specific network functions running in one or more VMs 1008 on the hardware 1004 and corresponds to an application 1002.

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

[0189] Figure 11 A communication diagram showing a host 1102 communicating with a UE 1106 via a network node 1104 over a partially wireless connection according to some embodiments. Figure 11 Describe the UE discussed in the previous paragraphs (such as Figure 6 UE612A and / or Figure 7 UE 700), network nodes (such as Figure 6 network node 610A and / or Figure 8 network nodes 800) and hosts (such as Figure 6 Host 616 and / or Figure 9 An example implementation of a host 900 according to various embodiments.

[0190] Similar to host 900, embodiments of host 1102 include hardware such as a communication interface, processing circuitry, and memory. Host 1102 also includes software that is stored in or accessible by host 1102 and that is executable by the processing circuitry. The software includes a host application that is operable to provide services to a remote user, such as a UE 1106 connected via an OTT connection 1150 extending between UE 1106 and host 1102. When providing services to the remote user, the host application may provide user data transmitted using OTT connection 1150.

[0191] The network node 1104 includes hardware that enables it to communicate with the host 1102 and the UE 1106 via a connection 1160. The connection 1160 may be direct or through a core network (such as Figure 6The core network 606 of the present invention and / or one or more other intermediate networks, such as one or more public, private or managed networks. For example, the intermediate network can be a backbone network or the Internet.

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

[0193] 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 connection 1160 and the wireless connection 1170 over which the OTT connection 1150 may be provided have been drawn abstractly to illustrate communications between the host 1102 and the UE 1106 via the network node 1104, without explicit reference to any intermediary devices and the precise routing of messages via those devices.

[0194] As an example of transmitting data via OTT connection 1150, in step 1108, host 1102 provides user data, which may be executed by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with UE 1106. In other embodiments, the user data is associated with UE 1106, which shares data with host 1102 without explicit human interaction. In step 1110, host 1102 initiates a transmission carrying the user data to UE 1106. Host 1102 may initiate the transmission in response to a request transmitted by UE 1106. The request may be initiated by human interaction with UE 1106 or by operation of a client application executing on UE 1106. In accordance with the teachings of embodiments described throughout this disclosure, the transmission may be delivered via network node 1104. Therefore, in step 1112, network node 1104 transmits the user data carried in the transmission initiated by host 1102 to 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 executing on the UE 1106 in association with a host application executed by the host 1102 .

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

[0196] One or more of the various embodiments use the OTT connection 1150 to improve the performance of the OTT service provided to the UE 1106, with the wireless connection 1170 forming the final segment. More specifically, the teachings of these embodiments can improve, for example, data rates, latency, power consumption, and the like, thereby providing benefits such as, for example, reduced user wait time, relaxed file size restrictions, improved content resolution, better responsiveness, extended battery life, and the like.

[0197] In an example scenario, plant status information may be collected and analyzed by the host 1102. As another example, the host 1102 may process audio and video data that has been acquired from the UE for use in creating a map. As another example, the host 1102 may collect and analyze real-time data to help control traffic congestion (e.g., controlling traffic lights). As another example, the host 1102 may store surveillance videos uploaded by the UE. As another example, the host 1102 may store or control access to media content, such as video, audio, VR, or AR that it may broadcast, multicast, or unicast to the UE. As other examples, the host 1102 may be used for energy pricing, remote control of non-time-critical electrical loads to balance power generation demand, location services, presentation services (such as compiled maps based on data collected from remote devices, etc.), or any other function of collecting, retrieving, storing, analyzing, and / or transmitting data.

[0198] In some examples, a measurement process may be provided for the purpose of monitoring data rate, latency, and other factors improved by one or more embodiments. Optional network functionality may also be present for reconfiguring the OTT connection 1150 between the host 1102 and the UE 1106 in response to changes in measurement results. The measurement process and / or network functionality for reconfiguring the OTT connection may be implemented in the software and hardware of the host 1102 and / or in the software and hardware of the UE 1106. In some embodiments, sensors (not shown) may be deployed in or associated with other devices through which the OTT connection 1150 passes; the sensors may participate in the measurement process by providing values ​​of the monitored quantities exemplified above or by providing values ​​of other physical quantities from which the software can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 1150 may include message formats, retransmission settings, preferred routing, etc.; reconfiguration does not require direct changes to the operation of the network node 1104. Such processes and functionality may be known and practiced in the art. In certain embodiments, the measurements may involve dedicated UE signaling that facilitates measurements of throughput, propagation time, latency, and the like by the host 1102. Such measurements are possible because software causes messages (particularly empty or "dummy" messages) to be transmitted using the OTT connection 1150 while monitoring propagation time, errors, etc.

[0199] Although the computing devices (e.g., UEs, network nodes, hosts) described herein may include combinations of the hardware components shown, other examples may include computing devices with different combinations of components. It should be understood that these computing devices may include any appropriate combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determination, calculation, acquisition, or similar operations described herein may be performed by processing circuitry that processes information by, for example, converting the acquired information into other information, comparing the acquired information or the converted information with information stored in the network node, and / or performing one or more operations based on the acquired information or the converted information, and making a determination as a result of the processing. In addition, although components are depicted as individual blocks within a larger block or nested within multiple blocks, in reality, a computing device may include multiple different physical components that constitute a single illustrated component, and functionality may be divided between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of a component may be divided between the processing circuitry and the communication interface. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0200] In certain embodiments, some or all of the functions described herein may be provided by a processing circuit that executes instructions stored in a memory, which in certain 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 a processing circuit without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those specific embodiments, the processing circuit may be configured to perform the described functionality regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functionality are not limited to separate processing circuits or other components of a computing device, but are enjoyed by the computing device as a whole and / or generally by end users and wireless networks.

[0201] Some example embodiments of the present disclosure are as follows: Group A Examples

[0202] Embodiment 1: A method in a wireless communication system, for allocating a subcarrier offset for a phase tracking reference signal (PT-RS) port in each resource block (RB) allocated for the PT-RS port, wherein when both the PT-RS and Rel 18 DMRS ports 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, the method comprising one or more of the following steps: • For a given higher layer configuration of associated DMRS ports and resource offset parameters, determine (500-A) the PT-RS subcarrier offset from an uplink UL table or a downlink DL table, wherein each table row is associated with the PT- The DMRS port associated with the RS; and • In case of Type 1 DMRS, PTRS of isolated RBs is supported (502-A) by the user equipment.

[0203] Embodiment 2: The method according to embodiment 1, wherein the DMRS port is one of type 1 or type 2.

[0204] Embodiment 3: The method according to embodiment 1, wherein the resource offset parameter is "resourceElementOffset".

[0205] Embodiment 4: A method in a wireless communication system for determining a power ratio of a phase tracking reference signal (PT-RS) to a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) per resource element (RE) per layer, wherein both the PT-RS and Rel 18 DMRS ports are configured for a UE, and the PDSCH or PUSCH is scheduled with at most 8 layers, the method comprising one or more of the following steps: According to the table, determine the PT-RS to PDSCH power ratio (500-B) per RE per layer for PDSCHs scheduled with 7 and 8 layers; For a partially coherent codebook, determine (502-B) a PT-RS to PUSCH power ratio per RE per layer that is specific to a PT-RS port or common to all PT-RS ports; o In the PT-RS port specific case, for each PT-RS port, the ratio is determined by the number of scheduled PUSCH layers associated with the PT-RS port and the total number of scheduled PT-RS ports associated with PUSCH; o In case of PT-RS port sharing, the ratio is determined 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 (504-B) the PT-RS to PUSCH power ratio per RE per layer by the number of scheduled PUSCH layers; and / or • For a non-coherent codebook, determining (506-B) the PT-RS to PUSCH power ratio per RE per layer is determined by the number of scheduled PTs. Group B Examples

[0206] Embodiment 5: A method performed by a network node, the method comprising any of the features of Group A embodiments.

[0207] Embodiment 6: The method according to any of the preceding embodiments further includes: obtaining user data; and forwarding the user data to a host or a user device. Group C Examples

[0208] Embodiment 7: A method performed by a user equipment, the method comprising any features of Group A embodiments. Group D Examples

[0209] Embodiment 8: A user equipment, comprising: a processing circuit configured to perform any steps of any embodiment in Group C of embodiments; and a power supply circuit configured to supply power to the processing circuit.

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

[0211] Embodiment 10: A user equipment (UE), the UE comprising: an antenna configured to send and receive wireless signals; a radio front-end circuit connected to the antenna and to a processing circuit and configured to condition signals transmitted between the antenna and the processing circuit; the processing circuit configured to perform any steps of any embodiment in Group C; an input interface connected to the processing circuit and configured to allow information to be input into the UE for processing by the processing circuit; an output interface connected to the processing circuit and configured to output information that has been processed by the processing circuit from the UE; and a battery connected to the processing circuit and configured to supply power to the UE.

[0212] Embodiment 11: A host configured to operate in a communication system to provide an over-the-top (OTT) service, 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), wherein the UE comprises a communication interface and a processing circuit, the communication interface and processing circuit of the UE being configured to perform any steps of any embodiment of Group V to receive user data from the host.

[0213] Embodiment 12: The host according to the previous embodiment, wherein the cellular network further comprises a network node configured to communicate with the UE to transmit user data from the host to the UE.

[0214] Embodiment 13: The host according to the first two embodiments, wherein: the processing circuit of the host is configured to execute a host application to provide user data; and the host application is configured to interact with a client application executed on the UE, and the client application is associated with the host application.

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

[0216] Embodiment 15: The method according to the previous embodiment further includes: executing, on the host, a host application associated with the client application executed on the UE to receive user data from the UE.

[0217] Embodiment 16: The method according to the previous embodiment further includes: at the host, transmitting input data to the client application executed on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

[0218] Embodiment 17: A host configured to operate in a communication system to provide an over-the-top (OTT) service, 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), wherein the UE comprises a communication interface and a processing circuit, the communication interface and processing circuit of the UE being configured to perform any steps of any embodiment in Group C to transmit the user data to the host.

[0219] Embodiment 18: The host according to the previous embodiment, wherein the cellular network further comprises a network node configured to communicate with the UE to transmit user data from the UE to the host.

[0220] Embodiment 19: The host according to the first two embodiments, wherein: the processing circuit of the host is configured to execute a host application to provide user data; and the host application is configured to interact with a client application executed on the UE, wherein the client application is associated with the host application.

[0221] Embodiment 20: A method implemented by a host configured to operate in a communication system that also includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host by the UE via the network node, wherein the UE performs any steps of any embodiment in Group C embodiments to transmit the user data to the host.

[0222] Embodiment 21: The method according to the previous embodiment further includes: executing, on the host, a host application associated with the client application executed on the UE to receive user data from the UE.

[0223] Embodiment 22: The method according to the previous embodiment further includes: at the host, transmitting input data to the client application executed on the UE, the input data being provided by executing the host application, wherein user data is provided by the client application in response to the input data from the host application.

[0224] Embodiment 23: A host configured to operate in a communication system to provide an over-the-top (OTT) service, 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 network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and a processing circuit, the processing circuit of the network node being configured to perform any operation of any embodiment in Group B to transmit the user data from the host to the UE.

[0225] Embodiment 24: The host according to the preceding embodiment, wherein: the processing circuit of the host is configured to execute a host application that provides user data; and the UE includes a processing circuit configured to execute a client application associated with the host application to receive transmission of the user data from the host.

[0226] Embodiment 25: A method implemented in a host configured to operate in a communication system that also includes a network node and a user equipment (UE), the method comprising: providing user data to the UE; and initiating transmission carrying the user data to the UE via a cellular network including the network node, wherein the network node performs any operation of any embodiment in Group B to transmit the user data from the host to the UE.

[0227] Embodiment 26: The method according to the previous embodiment further includes: transmitting, at the network node, user data provided by the host for the UE.

[0228] Embodiment 27: A method according to any of the preceding two embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executed on the UE, the client application being associated with the host application.

[0229] Embodiment 28: A communication system configured to provide over-the-top services, the communication system comprising a host, the host comprising: a processing circuit configured to provide user data to a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and a processing circuit, the processing circuit of the network node being configured to perform any operation of any embodiment in Group B to transmit the user data from the host to the UE.

[0230] Embodiment 29: The communication system according to the previous embodiment further includes: the network node; and / or the user equipment.

[0231] Embodiment 30: A host configured to operate in a communication system to provide an over-the-top (OTT) service, 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 being configured to perform any operation of any embodiment in Group B to receive user data from a user equipment (UE) of the host.

[0232] Embodiment 31: The host according to the first two embodiments, wherein: the processing circuit of the host is configured to execute a host application to provide user data; and the host application is configured to interact with a client application executed on the UE, and the client application is associated with the host application.

[0233] Embodiment 32: The host according to any of the preceding two embodiments, wherein initiating receipt of user data comprises requesting user data.

[0234] Embodiment 33: A method implemented by a host configured to operate in a communication system that also includes a network node and a user equipment (UE), the method comprising: at the host, initiating reception of user data from the UE, the user data originating from a transmission received by the network node from the UE, wherein the network node performs any steps of any embodiment in Group B embodiments to receive user data of the UE from the host.

[0235] Embodiment 34: The method according to the previous embodiment further includes: at the network node, transmitting the received user data to the host.

[0236] 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 to be within the scope of the concepts disclosed herein.

Claims

1. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: For each of the one or more resource blocks (RBs) allocated for a phase tracking reference signal (PT-RS) port configured for the UE: o Determining (500-A; 500-B) 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 configured for the UE, and a resource element offset parameter, wherein: ■ the DMRS port associated with the PT-RS port is one of a plurality of DMRS ports, wherein eight of the plurality of DMRS ports are associated to a first DMRS configuration type and twelve of the plurality of DMRS ports are associated to a second DMRS configuration type; and ■ each row of the table is associated with one of the plurality of DMRS ports and defines, for different resource element offset parameter values ​​of at least one of the first DMRS configuration type and the second DMRS configuration type, a different PT-RS subcarrier offset for a PT-RS port associated with the one of the plurality of DMRS ports; o According to the determined PT-RS subcarrier offset, transmit or receive (502-B) PT-RS on the PT-RS port in the RB.

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

3. The method according to claim 2, wherein: The plurality of DMRS ports include DMRS ports 0 to 17, and the uplink table includes: • A row associated to DMRS port 8, which defines: ○ For the first DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 4; ○ For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 6; o For the first DMRS configuration type, the resource offset parameter value is '10', and the PT-RS subcarrier offset is 10; and ○ For the first DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 0; • A row associated to DMRS port 9, which defines: ○ For the first DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 6; ○ For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 8; o For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 0; and ○ For the first DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 2; • A row associated to DMRS port 10, which defines: ○ For the first DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 5; ○ For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 7; o For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 11; and ○ For the first DMRS configuration type, the resource offset parameter value is '11', and the PT-RS subcarrier offset is 1; A row associated to DMRS port 11, which defines: ○ For the first DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 7; ○ For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 9; o For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 1; and ○ For the first DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 3; • A row associated to DMRS port 12, which defines: ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 6; ○ For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 7; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 0; and ○ For the second DMRS configuration type, the resource offset parameter value is '11', and the PT-RS subcarrier offset is 1; • A row associated to DMRS port 13, which defines: ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 7; ○ For the second DMRS configuration type, the resource offset parameter value is '01', and the PT-RS subcarrier offset is 0; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 1; and ○ For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 6; • A row associated to DMRS port 14, which defines: ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 8; ○ For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 9; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 2; and ○ For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 3; • A row associated to DMRS port 15, which defines: ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 9; ○ For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 2; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 3; and ○ For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 8; • A row associated to DMRS port 16, which defines: ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 10; ○ For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 11; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 4; and o For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 5; and • A row associated to DMRS port 17, which defines: ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 11; ○ For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 4; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 5; and For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 10.

4. The method according to claim 3, wherein: The uplink table also includes: A row associated with DMRS port 0, which defines: ○ For the first DMRS configuration type, the resource offset parameter value is '00', and the PT-RS subcarrier offset is 0; ○ For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 2; ○ For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 6; ○ For the first DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 8; ○ For the second DMRS configuration type, the resource offset parameter value is '00', and the PT-RS subcarrier offset is 0; ○ For the second DMRS configuration type, the resource offset parameter value is '01', and the PT-RS subcarrier offset is 1; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 6; and ○ For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 7; A row associated to DMRS port 1, which defines: ○ For the first DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 2; ○ For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 4; ○ For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 8; ○ For the first DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 10; ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 1; ○ For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 6; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 7; and ○ For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 0; A row associated to DMRS port 2, which defines: ○ For the first DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 1; ○ For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 3; ○ For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 7; ○ For the first DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 9; ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 2; ○ For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 3; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 8; and ○ For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 9; • A row associated to DMRS port 3, which defines: ○ For the first DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 3; ○ For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 5; ○ For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 9; ○ For the first DMRS configuration type, the resource offset parameter value is '11', and the PT-RS subcarrier offset is 11; ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 3; ○ For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 8; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 9; and ○ For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 2; • A row associated to DMRS port 4, which defines: ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 4; ○ For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 5; o For the second DMRS configuration type, the resource offset parameter value is '10', and the PT-RS subcarrier offset is 10; and o For the second DMRS configuration type, the resource offset parameter value is '11', and the PT-RS subcarrier offset is 11; and • A row associated to DMRS port 5, which defines: ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 5; ○ For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 10; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 11; and ○ For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 4.

5. The method according to claim 1, wherein The table is a downlink table associated with a physical downlink shared channel PDSCH transmission, and wherein the one or more RBs are N scheduled for the PDSCH. RB A subset of ≥1 RBs.

6. The method according to claim 5, wherein: The plurality of DMRS ports include DMRS ports 0 to 17, and the downlink table includes: • A row associated to DMRS port 1008, which defines: ○ For the first DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 4; ○ For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 6; o For the first DMRS configuration type, the resource offset parameter value is '10', and the PT-RS subcarrier offset is 10; and ○ For the first DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 0; • A row associated to DMRS port 1009, which defines: ○ For the first DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 6; ○ For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 8; o For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 0; and ○ For the first DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 2; • A row associated to DMRS port 1010, which defines: ○ For the first DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 5; ○ For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 7; o For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 11; and ○ For the first DMRS configuration type, the resource offset parameter value is '11', and the PT-RS subcarrier offset is 1; • A row associated to DMRS port 1011, which defines: ○ For the first DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 7; ○ For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 9; o For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 1; and ○ For the first DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 3; • A row associated to DMRS port 1012, which defines: ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 6; ○ For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 7; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 0; and ○ For the second DMRS configuration type, the resource offset parameter value is '11', and the PT-RS subcarrier offset is 1; • A row associated to DMRS port 1013, which defines: ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 7; ○ For the second DMRS configuration type, the resource offset parameter value is '01', and the PT-RS subcarrier offset is 0; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 1; and ○ For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 6; • A row associated to DMRS port 1014, which defines: ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 8; ○ For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 9; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 2; and ○ For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 3; • A row associated to DMRS port 1015, which defines: ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 9; ○ For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 2; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 3; and ○ For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 8; • A row associated to DMRS port 1016, which defines: ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 10; ○ For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 11; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 4; and o For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 5; and • A row associated to DMRS port 1017, which defines: ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 11; ○ For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 4; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 5; and ○ For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 10.

7. The method according to claim 6, wherein: The uplink table also includes: A row associated to DMRS port 1000, which defines: ○ For the first DMRS configuration type, the resource offset parameter value is '00', and the PT-RS subcarrier offset is 0; ○ For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 2; ○ For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 6; ○ For the first DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 8; ○ For the second DMRS configuration type, the resource offset parameter value is '00', and the PT-RS subcarrier offset is 0; ○ For the second DMRS configuration type, the resource offset parameter value is '01', and the PT-RS subcarrier offset is 1; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 6; and ○ For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 7; A row associated to DMRS port 1001, which defines: ○ For the first DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 2; ○ For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 4; ○ For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 8; ○ For the first DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 10; ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 1; ○ For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 6; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 7; and ○ For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 0; • A row associated to DMRS port 1002, which defines: ○ For the first DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 1; ○ For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 3; ○ For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 7; ○ For the first DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 9; ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 2; ○ For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 3; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 8; and ○ For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 9; • A row associated to DMRS port 1003, which defines: ○ For the first DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 3; ○ For the first DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 5; ○ For the first DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 9; ○ For the first DMRS configuration type, the resource offset parameter value is '11', and the PT-RS subcarrier offset is 11; ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 3; ○ For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 8; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 9; and ○ For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 2; • A row associated to DMRS port 1004, which defines: ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 4; ○ For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 5; o For the second DMRS configuration type, the resource offset parameter value is '10', and the PT-RS subcarrier offset is 10; and o For the second DMRS configuration type, the resource offset parameter value is '11', and the PT-RS subcarrier offset is 11; and • A row associated to DMRS port 1005, which defines: ○ For the second DMRS configuration type, the resource offset parameter value is '00' and the PT-RS subcarrier offset is 5; ○ For the second DMRS configuration type, the resource offset parameter value is '01' and the PT-RS subcarrier offset is 10; o For the second DMRS configuration type, the resource offset parameter value is '10' and the PT-RS subcarrier offset is 11; and ○ For the second DMRS configuration type, the resource offset parameter value is '11' and the PT-RS subcarrier offset is 4.

8. The method according to any one of claims 1 to 7, wherein Mapping the PT-RS port to a DMRS subcarrier of the associated DMRS port in each of the one or more RBs allocated to the PT-RS port, wherein the one DMRS subcarrier to which the PT-RS port in each RB is mapped is defined as a function of the determined PT-RS subcarrier offset.

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

10. The method according to any one of claims 1 to 8, wherein For scheduling, there is N RB (≥1) RBs of PDSCH or PUSCH, the N RB The corresponding The subcarriers are ordered from 0 to are numbered, and the N RB The subcarrier to which the PTRS port is mapped in an RB is given by: in: ● 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} ● is the RB offset of PT-RS and is given by ● is the number of subcarriers per RB ●n RNTI is the RNTI associated with the DCI that schedules the transmission.

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

12. The method according to 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 on this, the UE assumes that no PT-RS is present in the RB.

13. The method according to claim 11, wherein The RB is scheduled for downlink and the determined PT-RS subcarrier offset exceeds the allowed range of 0 to 7 and includes 0 to 7, and based on this, the UE assumes that there is no PT-RS in the RB with the lowest index in each set of consecutively scheduled RBs, and assumes that PT-RS is present in the remaining RBs.

14. The method according to 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 and inclusive, and based on this, the UE assumes that no PT-RS is present in the RB if the RB is associated with an isolated resource element.

15. The method according to 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 on this, the UE does not transmit PT-RS in the RB.

16. The method according to claim 11, wherein The RB is scheduled for downlink, and the determined PT-RS subcarrier offset exceeds the allowed range of 0 to 7 and includes 0 to 7, and based on this, the UE does not transmit the PT-RS in the RB with the highest index in each set of consecutively scheduled RBs, but transmits the PT-RS in the remaining RBs.

17. The method according to claim 11, wherein The RB is scheduled for downlink and the determined PT-RS subcarrier offset exceeds the allowed range of 0 to 7 and includes 0 to 7, and based on this, the UE does not transmit the PT-RS in the RB with the lowest index in each set of consecutively scheduled RBs, but transmits the PT-RS in the remaining RBs.

18. A user equipment (UE) for a wireless communication system, the UE being adapted to: For each of the one or more resource blocks (RBs) allocated for a phase tracking reference signal (PT-RS) port configured for the UE: o Determining (500-A; 500-B) 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 configured for the UE, and a resource element offset parameter, wherein: ■ the DMRS port associated with the PT-RS port is one of a plurality of DMRS ports, wherein eight of the plurality of DMRS ports are associated to a first DMRS configuration type and twelve of the plurality of DMRS ports are associated to a second DMRS configuration type; and ■ each row of the table is associated with one of the plurality of DMRS ports and defines, for different resource element offset parameter values ​​of at least one of the first DMRS configuration type and the second DMRS configuration type, a different PT-RS subcarrier offset for a PT-RS port associated with the one of the plurality of DMRS ports; o According to the determined PT-RS subcarrier offset, transmit or receive (502-B) PT-RS on the PT-RS port in the RB.

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

20. A user equipment (UE) (700) for a wireless communication system, the UE (700) comprising: A communication interface (712) comprising a transmitter (718) and a receiver (720); as well as a processing circuit (702) associated with the communication interface (712), the processing circuit (702) being configured to cause the UE (700) to, for each of one or more resource blocks (RBs) allocated for a phase tracking reference signal (PT-RS) port configured for the UE: o Determining (500-A; 500-B) 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 configured for the UE, and a resource element offset parameter, wherein: ■ the DMRS port associated with the PT-RS port is one of a plurality of DMRS ports, wherein eight of the plurality of DMRS ports are associated to a first DMRS configuration type and twelve of the plurality of DMRS ports are associated to a second DMRS configuration type; and ■ each row of the table is associated with one of the plurality of DMRS ports and defines, for different resource element offset parameter values ​​of at least one of the first DMRS configuration type and the second DMRS configuration type, a different PT-RS subcarrier offset for a PT-RS port associated with the one of the plurality of DMRS ports; o According to the determined PT-RS subcarrier offset, transmit or receive (502-B) PT-RS on the PT-RS port in the RB.

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

22. A method performed by a network node in a wireless communication system, the method comprising: For each of the one or more resource blocks (RBs) allocated for a phase tracking reference signal (PT-RS) port configured for a user equipment (UE): o Determining (500-A; 500-B) 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 configured for the UE, and a resource element offset parameter, wherein: ■ the DMRS port associated with the PT-RS port is one of a plurality of DMRS ports, wherein eight of the plurality of DMRS ports are associated to a first DMRS configuration type and twelve of the plurality of DMRS ports are associated to a second DMRS configuration type; and ■ each row of the table is associated with one of the plurality of DMRS ports and defines, for different resource element offset parameter values ​​of at least one of the first DMRS configuration type and the second DMRS configuration type, a different PT-RS subcarrier offset for a PT-RS port associated with the one of the plurality of DMRS ports; o According to the determined PT-RS subcarrier offset, transmit or receive (502-B) PT-RS on the PT-RS port in the RB.

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

24. The method according to claim 23, wherein The PxSCH transmission is a physical downlink shared channel PDSCH transmission with 7 or 8 layers, the determined PT-RS to PxSCH power ratio per RE per spatial layer is the PT-RS to PDSCH power ratio per RE per spatial layer, and the transmitting node is a network node in the wireless communication system.

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

26. The method according to 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', wherein 'EPRE-ratio' is signaled from the network node to the UE and may have an integer value from 0 to 3.

27. The method according to claim 25 or 26, wherein The table definition: For the case where the PDSCH transmission consists of 7 spatial layers, the PT-RS to PDSCH power ratio per RE per spatial layer is 8.45; and For the case where the PDSCH transmission consists of 8 spatial layers, the PT-RS to PDSCH power ratio per RE per spatial layer is 9.

28. The method according to claim 27, wherein The table also defines: For the case where the PDSCH transmission consists of 1 spatial layer, the PT-RS to PDSCH power ratio per RE per spatial layer is 0; For the case where the PDSCH transmission consists of two spatial layers, the PT-RS to PDSCH power ratio per RE per spatial layer is 3; For the case where the PDSCH transmission consists of three spatial layers, the PT-RS to PDSCH power ratio per RE per spatial layer is 4.77; For the case where the PDSCH transmission consists of 4 spatial layers, the PT-RS to PDSCH power ratio per RE per spatial layer is 6; For the case where the PDSCH transmission consists of 5 spatial layers, the PT-RS to PDSCH power ratio per RE per spatial layer is 7; For the case where the PDSCH transmission consists of 6 spatial layers, the PT-RS to PDSCH power ratio per RE per spatial layer is 7.

78.

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

30. The method according to any one of claims 25 to 29, wherein Determining (500-D) the PT-RS to PDSCH power ratio per RE per spatial layer of the scheduled PDSCH transmission having 7 or 8 spatial layers includes: determining a row in the table based on the configured parameter 'EPRE-ratio', and determining the PT-RS to PDSCH power ratio value per RE per spatial layer in the determined row based on the number of spatial layers of the PDSCH.

31. The method of claim 23, wherein: The PxSCH transmission is a physical uplink shared channel PUSCH transmission at the UE with up to 8 layers and on up to 8 antenna ports, the determined PT-RS to PxSCH power ratio per RE per spatial layer is the PT-RS to PUSCH power ratio per RE per spatial layer, and the transmitting node is the UE.

32. The method according to claim 31, wherein Determining (500-D) the PT-RS to PUSCH power ratio per RE per spatial layer of the scheduled PUSCH transmission is based on a table, which defines multiple PT-RS to PUSCH power ratio values ​​per RE per spatial layer for corresponding multiple numbers 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. The method according to 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. The method according to claim 33, wherein For fully coherent PUSCH transmission on the up to 8 antenna ports, each of the plurality of PT-RS to PUSCH power ratio values ​​per RE per spatial layer in at least one of the one or more rows in the table is calculated based on a corresponding number of PUSCH spatial layers associated with the PT-RS port, as defined by the following equation: in, is the PT-RS to PUSCH power ratio per RE per spatial layer, and is the number of spatial layers in the PUSCH transmission.

35. The method of claim 33, wherein: For non-coherent PUSCH transmission on the at most 8 antenna ports, each spatial layer of the PUSCH transmission is transmitted only on one of the at most 8 antenna ports, and each of the multiple PT-RS to PUSCH power ratio values ​​per RE per spatial layer 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 the following formula: in, is the PT-RS to PUSCH power ratio per RE per spatial layer, and Q p is the number of PT-RS ports scheduled for PUSCH transmission.

36. The method of claim 33, wherein: For partially coherent PUSCH transmission on the at most 8 antenna ports, the at most 8 antenna ports of the UE are divided into two or more antenna port groups, and PUSCH transmissions in each of the groups are coherent, and each of the multiple PT-RS to PUSCH power ratio values ​​per RE per spatial layer in at least one of the one or more rows in the table is calculated based on a corresponding number of PUSCH spatial layers in the same antenna group as the PT-RS, as defined by the following formula: in, is the PT-RS to PUSCH power ratio per RE per spatial layer, is the number of spatial layers of the PUSCH 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.

37. The method according to claims 32 to 36, wherein Determining (500-D) the PT-RS to PUSCH power ratio per RE per spatial layer of the scheduled PUSCH transmission includes: determining the rows 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 the PT-RS to PUSCH power ratio value per RE per spatial layer based on the corresponding 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, the transmitting node (610; 612) being adapted to: Determine (500-D) a phase tracking reference signal PT-RS to PxSCH power ratio per resource element RE per spatial layer for physical downlink / uplink shared channel PxSCH transmission for scheduling of user equipment UE, wherein The PxSCH transmission has at most 8 spatial layers and is on more than 4 antenna ports; transmitting (502-D) said scheduled PxSCH transmission having up to 8 layers; The PT-RS is transmitted (504-D) on the PT-RS port along with the PxSCH transmission at a transmit power according to the determined PT-RS to PxSCH power ratio per RE per spatial layer.

39. The 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, the transmitting node (610; 612; 700; 800) comprising a processing circuit (702; 802) configured such that the transmitting node (610; 612; 700; 800): Determine (500-D) a phase tracking reference signal PT-RS to PxSCH power ratio per resource element RE per spatial layer for physical downlink / uplink shared channel PxSCH transmission for scheduling of user equipment UE, wherein The PxSCH transmission has at most 8 spatial layers and is on more than 4 antenna ports; transmitting (502-D) said scheduled PxSCH transmission having up to 8 layers; The PT-RS is transmitted (504-D) on the PT-RS port along with the PxSCH transmission at a transmit power according to the determined PT-RS to PxSCH power ratio per RE per spatial layer.

Images