Signaling indicating identifiers of at least five uplink DMRS ports

Abstract

A wireless device (WD) allocates a demodulation reference signal (DMRS) port for physical uplink shared channel (RUSCH) transmission. The WD receives an identifier (X, X + 1, X + 2) for an antenna port table for scheduling uplink DMRS ports, the identifier indicating an allocation of at least five DMRS ports for at least five corresponding RUSCH layers, where the DMRS ports belong to one or more code division multiplexing (CDMM) groups. The WD determines a DMRS port configuration based on the identifier, and transmits a DMRS symbol in accordance with the determined DMRS port configuration.

Description

Technical Field

[0001] The present disclosure relates to wireless communications, and more particularly to antenna port entries / configurations for more than four layers of the Physical Uplink Shared Channel (PUSCH). Background Art

[0002] The Third Generation Partnership Project (3GPP) has developed and is currently developing standards for fourth-generation (4G) (also known as Long Term Evolution (LTE)) and fifth-generation (5G) (also known as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes (NN), such as base stations, and mobile wireless devices (WDs), as well as communication between network nodes and between WDs. 3GPP is also developing standards for sixth-generation (6G) wireless communication networks.

[0003] NR frame structure and resource grid

[0004] Some existing NR systems use cyclic prefix orthogonal frequency domain multiplexing (CP-OFDM) in both the downlink (i.e., from the network node gNB or base station to the WD) and the uplink (i.e., from the WD to the network node). Direct Fourier transform (DFT)-extended OFDM is also supported in the uplink. In the time domain, the NR downlink and uplink can be organized into equally sized subframes of 1 ms each. The subframes can be further divided into multiple slots of equal duration. The slot length depends on the subcarrier spacing. For example, for a subcarrier spacing of Δf = 15 kHz, each subframe can have only one slot, where each slot includes 14 OFDM symbols.

[0005] Data scheduling in NR is typically on a slot basis, where the first two symbols contain the Physical Downlink Control Channel (PDCCH) and the remaining symbols contain the Physical Shared Data Channel (either Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH)). Figure 1 is a timing diagram of an example NR time domain structure with 15 kHz subcarrier spacing, depicting an example slot configuration including 14-symbol slots.

[0006] Different subcarrier spacing values can be supported in NR. The supported subcarrier spacing values (also known as different parameter sets) are given by Δf = (15 × 2 μ )kHz, where μ∈0,1,2,3,4. Δf=15kHz is the basic subcarrier spacing. The time slot duration under different subcarrier spacing is given by Given.

[0007] In the frequency domain, the system bandwidth is divided into resource blocks (RBs), each corresponding to 12 consecutive subcarriers. RBs are numbered starting from 0, starting from one end of the system bandwidth. One OFDM subcarrier during one OFDM symbol period forms one resource element (RE). Figure 2 is a diagram illustrating an example NR physical time-frequency resource grid, where only one resource block (RB) within a 14-symbol slot is shown.

[0008] Downlink (DL) PDSCH transmissions can be either dynamically scheduled, i.e., in each slot, the network node / gNB transmits downlink control information (DCI) on the physical downlink control channel (PDCCH) regarding to which WD the data is to be transmitted and on which RBs in the current downlink slot the data is to be transmitted; or semi-persistently scheduled (SPS), where periodic PDSCH transmissions are activated or deactivated by DCI. In NR, different DCI formats are defined for DL PDSCH scheduling, including, for example, DCI format 1_0, DCI format 1_1, and DCI format 1_2.

[0009] Similarly, uplink grants carried in PDCCH can also be used to schedule uplink (UL) PUSCH transmissions either dynamically or semi-persistently. NR supports two types of semi-persistent uplink transmissions, namely, Type 1 Configuration Grant (CG) and Type 2 Configuration Grant, where Type 1 Configuration Grant is configured and activated by Radio Resource Control (RRC), while Type 2 Configuration Grant is configured by RRC but activated / deactivated by DCI. DCI formats used to schedule PUSCH include, for example, DCI format 0_0, DCI format 0_1, and DCI format 0_2.

[0010] DMRS configuration

[0011] Demodulation Reference Signals (DM-RS) can be used for coherent demodulation of physical layer data channels (i.e., Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH)) and Physical Downlink Control Channel (PDCCH). DM-RS can be confined to the resource blocks carrying the associated physical layer channels and can be mapped to the allocated resource elements of the time-frequency resource grid, allowing the receiver to efficiently handle time / frequency selective fading of the radio channel.

[0012] The mapping of DM-RS to resource elements is configurable in both the frequency and time domains. For example, in some existing systems, there are two mapping types in the frequency domain: Type 1 and Type 2. Furthermore, there are two mapping types in the time domain: Type A and Type B, which define the symbol position of the first OFDM symbol containing the DM-RS within a transmission period.

[0013] DM-RS mapping in the time domain can further be based on single symbols or dual symbols, where the latter means that the DM-RS is mapped to a pair of two adjacent OFDM symbols. For single-symbol-based DMRS, one, two, three, or four single-symbol DM-RSs can be configured for a WD in a time slot. For dual-symbol-based DMRS, one or two such dual-symbol DM-RSs can be configured for a WD in a time slot. In scenarios with low Doppler, it may be sufficient to configure only the leading DM-RS (i.e., one single-symbol DM-RS or one dual-symbol DM-RS), while in scenarios with high Doppler, additional DM-RSs will be required in a time slot.

[0014] Figure 3 Examples of type 1 preamble DM-RS with a single symbol (chart a), type 1 preamble dual-symbol DM-RS (chart b), type 2 preamble single-symbol DM-RS (chart c), and type 2 preamble dual-symbol DM-RS (chart d) are shown. Figure 3 FIG. 1 shows a time domain mapping type A with a first DM-RS in the third OFDM symbol of a 14-symbol transmission period. Figure 3 Type 1 and Type 2 differ in terms of mapping structure and the number of supported DM-RS code division multiplexing (CDM) groups, where Type 1 supports 2 CDM groups and Type 2 supports 3 CDM groups.

[0015] DM-RS antenna ports can be mapped to resource elements within only one CDM group. For single-symbol DM-RS, two antenna ports can be mapped to each CDM group, while for dual-symbol DM-RS, four antenna ports can be mapped to each CDM group. Therefore, for DM-RS Type 1, the maximum number of DM-RS ports is four for a single-symbol DMRS configuration and eight for a dual-symbol DMRS configuration. For DM-RS Type 2, the maximum number of DM-RS ports is six for a single-symbol DMRS configuration and twelve for a dual-symbol DMRS configuration.

[0016] For example, an orthogonal cover code (OCC) with a length of 2 (i.e., [+1, +1] or [+1, -1]) can be used to separate antenna ports mapped in the same two resource elements within a CDM group. When dual-symbol DM-RS is configured, OCC can be applied in the frequency domain (FD) and / or in the time domain (TD). For example, this Figure 3 It is shown for CDM group 0.

[0017] In 3GPP NR Technology Release 15 (3GPP Rel-15), for parameter set index μ, the mapping of PDSCH DM-RS sequence r(m), m=0, 1, ... to antenna port p and subcarrier k in OFDM symbol l is specified in 3GPP Technical Standard (TS) 38.211 as: k'=0,1 n=0,1,…… Among them, w f (k') represents the frequency domain length 2 OCC code, and w t (l') represents a time domain length 2 OCC code. Tables 1 and 2 below list the PDSCH DM-RS mapping parameters for configuring type 1 and type 2, respectively. Table 1: PDSCH DM-RS mapping parameters for configuration type 1. Table 2: PDSCH DM-RS mapping parameters for configuration type 2.

[0018] For PDSCH mapping type A, DM-RS mapping is relative to the slot boundary. That is, the first leading DM-RS symbol in DM-RS mapping type A is in either the third or fourth symbol of the slot. In addition to the leading DM-RS, type A DM-RS mapping may also include up to three additional DM-RSs. If the scheduled PDSCH duration is shorter than a full slot, the DMRS position is changed according to the specification (i.e., 3GPP TS 38.211).

[0019] Figure 4 is a timing diagram showing an example of DM-RS configuration for PDSCH mapping type A. Figure 4 The examples in assume that the PDSCH duration is a full slot. In the examples, a PDSCH length of 14 symbols is assumed, however other symbol lengths may also be utilized.

[0020] Figure 5 is a timing diagram showing an example of a DM-RS configuration for PDSCH mapping type B. For PDSCH mapping type B, DM-RS mapping is relative to the start of transmission. That is, the first DM-RS symbol in DM-RS mapping type B is in the first symbol where type B PDSCH starts. Figure 5 Some examples of DM-RS for mapping type A are shown in FIG.

[0021] When transform precoding is not enabled, the same DMRS design used for PDSCH can also be applied to PUSCH, where the sequence r(m) can be mapped to the DMRS ports according to the following formula: The intermediate amount k′=0,1 n=0,1,…… j=0, 1, ..., υ-1 Among them, w f (k'), w t (l') and Δ are given by Tables 6.4.1.1.3-1 and 6.4.1.1.3-2 in 3GPP TS 38.211 (copied below as Tables 3A and 3B), and v is the number of PUSCH transmission layers. If Δ corresponds to For any other antenna port other than

[0022] The intermediate amount Precoding, multiplied by the amplitude scaling factor In order to comply with the transmit power specified in clause 6.2.2 of 3GPP TS 38.214, and mapped to physical resources according to the following formula in: - The precoding matrix W is given by clause 6.3.1.5 of 3GPP TS 38.211; -{p0,....,p ρ -1} is the set of physical antenna ports used to transmit PUSCH; and - It is the set of DMRS ports used for PUSCH. Table 3A: Parameters for PUSCH DM-RS configuration type 1. Table 3B: Parameters for PUSCH DM-RS configuration type 2.

[0023] DMRS sequence generation

[0024] The DMRS sequence r(n) used for both PDSCH and PUSCH is defined by: The pseudo-random sequence c(i) is defined in clause 5.2.1 of 3GPP TS 38.211. The pseudo-random sequence generator is initialized using the following formula: Where l is the OFDM symbol number in the time slot, is the timeslot number within the frame: and For PDSCH DMRS, given by the higher layer parameters scramblingID0 and scramblingID1 in the DMRS-DownlinkConfig IE (if provided), respectively And PDSCH is scheduled by PDCCH using DCI format 1_1 or 1_2 with CRC scrambled by C-RNTI, MCS-C-RNTI or CS-RNTI; For PUSCH DMRS, given by the higher layer parameters scramblingID0 and scramblingID1 in the DMRS-UplinkConfig IE (if provided), respectively and PUSCH is scheduled by DCI format 0_1 or 0_2 or by PUSCH transmission with configuration grant; For PDSCH DMRS, given by the higher layer parameter scramblingID0 in the DMRS-DownlinkConfig IE (if provided) And PDSCH is used by PDCCH with C- RNTI, MCS-C-RNTI or CS-RNTI scrambled CRC DCI format 1_0 for scheduling; For PUSCH DMRS, given by the higher layer parameter scramblingID0 in the DMRS-UplinkConfig IE (if provided) and PUSCH is scheduled by DCI format 0_1 or 0_2 or by PUSCH transmission with configuration grant; · otherwise; · and is given by: o If the higher layer parameter dmrs-Downlink in the DMRS-DownlinkConfig IE or dmrs-Uplink in the DMRS-UplinkConfig IE is provided, the corresponding and Identified as: where λ is the CDM group index; oOtherwise, it is given by:

[0025] Quantity n SCID ∈{0,1}, given by the DM-RS Sequence Initialization field (if present) in the DCI associated with the PDSCH transmission if DCI format 1_1 or 1_2 is used, or by the PUSCH transmission if DCI format 0_1 or 0_2 is used, or indicated by the higher layer parameter dmrs-SeqInitialization (if present) for type 1 PUSCH transmission with configured grant; otherwise s SCID =0.

[0026] DMRS port signaling

[0027] The DMRS port(s) used for PDSCH or PUSCH are signaled in the corresponding scheduling DCI.In addition to the DMRS ports, the number of CDM groups not allocated to PDSCH or PUSCH and the number of pre-DMRS symbols are also dynamically signaled in the DCI.

[0028] In PUSCH scheduling, the layer number is specified separately from the DMRS port signaling in the DCI, whereas for PDSCH scheduling, the layer number and DMRS port are jointly signaled in the DCI.

[0029] The "Antenna Port(s)" bit field in the DCI is used. Examples of Type 1 DMRS for PUSCH with rank = 1 and a maximum number of leading DMRS OFDM symbols up to 2 are shown below in Tables 4 and 5. These tables are copied from 3GPP TS 38.212. In this example, 4 bits are used. Note that the DMRS type and the maximum number of leading DMRS symbols are semi-statically configured by RRC. Table 4: Antenna port(s), transform precoder disabled, dmrs-Type=1, maxLength=2, rank=1 Table 5: Antenna port(s), transform precoder disabled, dmrs-Type=1, maxLength=2, rank=2

[0030] Another example of Type 1 DMRS with a maximum number of leading DMRS OFDM symbols up to 2 for PDSCH is shown below in Table 6, which is copied from 3GPP TS 38.212. Table 6: (One or more) antenna ports (1000 + DMRS port), dmrs-Type = 1, maxLength = 2 (From 3GPP TS 38.212)

[0031] DMRS protocol in Rel-18

[0032] It has been agreed in RAN1#110-bis that 3GPP Technology Release 18 (3GPP Rel-18) DMRS will use an extended frequency division duplex orthogonal cover code (FD-OCC) length of 4 per CDM group instead of an FD-OCC length of 2. The FD code will either be based on a Walsh matrix (Hadamard code), as shown in the example below in Table 7. Table 7: Walsh matrix for length 4 FD-OCC (Hadamard code)

[0033] Alternatively, the cyclic shift may be configured using {0, π / 2, π, 3π / 2} as shown in Table 8 below. Table 8: Cyclic shifts using {0, π, π / 2, 3π / 2} for length 4 FD-OCC

[0034] It has been further agreed that 3GPP Rel-18 DMRS ports identical to 3GPP Rel-15 DMRS ports should have the same antenna port number, while new 3GPP Rel-18 DMRS ports should use new antenna port numbers. This is shown in Tables 9 and 10 below, which show the agreement from RAN1#110-bis for DMRS Type 1 and DMRS Type 2, respectively. Note that the codes corresponding to the FD-OCC index can be found in Tables 7 and 8: p CDM group index FD-OCC Index TD-OCC Index 0 0 0 0 1 0 1 0 2 1 0 0 3 1 1 0 4 0 0 1 5 0 1 1 6 1 0 1 7 1 1 1 8 0 2 0 9 0 3 0 10 1 2 0 11 1 3 0 12 0 2 1 13 0 3 1 14 1 2 1 15 1 3 1 Table 9: Negotiated antenna port numbers for Rel-18 DMRS type 1 p CDM group index FD-OCC Index TD-OCC Index 0 0 0 0 1 0 1 0 2 1 0 0 3 1 1 0 4 2 0 0 5 2 1 0 6 0 0 1 7 0 1 1 8 1 0 1 9 1 1 1 10 2 0 1 11 2 1 1 12 0 2 0 13 0 3 0 14 1 2 0 15 1 3 0 16 2 2 0 17 2 3 0 18 0 2 1 19 0 3 1 20 1 2 1 21 1 3 1 22 2 1 1 23 3 3 1 Table 10: Negotiated antenna port numbers for Rel-18 DMRS type 2

[0035] Terminology about eType1 and eType2

[0036] 3GPP discussions have considered the following terminology for 3GPP Rel-18 DMRS, i.e., eType 1 and eType 2 DMRS ports: For discussion purposes, example definitions for 3GPP Rel-15 DMRS ports and 3GPP Rel-18 DMRS ports are: o 3GPP Rel-15 Type 1 / Type 2 DMRS port: uses a DMRS port with FD-OCC length = 2; o 3GPP Rel-18eType 1 / eType 2 DMRS port: Use a DMRS port with an FD-OCC length greater than 2.

[0037] Figure 6 is a diagram illustrating example differences between a 3GPP Rel-15 Type 1 DMRS port and a 3GPP Rel-18e Type 1 DMRS port.

[0038] In NR, antenna port tables for 3GPP Rel-15 Type 1 / Type 2 DMRS ports are specified. However, existing systems lack a mechanism for determining / selecting antenna port tables for 3GPP Rel-18 eType 1 / eType 2 DMRS ports in an efficient manner. Summary of the Invention

[0039] Some embodiments advantageously provide methods, systems, and apparatus for determining antenna port entries for more than four layers of PUSCH.

[0040] One or more embodiments describe solutions for how to signal from the network to the WD the DMRS ports to be used for scheduled PUSCH transmissions when the WD is configured with an expanded number of orthogonal DMRS ports (e.g., as will be specified in 3GPP Rel-18). The WD may be scheduled with more than four PUSCH layers.

[0041] According to one aspect, a method for allocating DMRS antenna ports for PUSCH transmission when more than four PUSCH layers are scheduled is described. The method comprises: Receiving an indication of a codepoint for the antenna port field in the DCI for scheduling a PUSCH, the indication indicating at least one of the following: o 5 spatial layers o 6 spatial layers o 7 spatial layers o 8 spatial layers The DMRS port is transmitted according to the code point indication of the antenna port field.

[0042] In some embodiments, for 5 spatial layers, three DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group. The two DMRS ports in the second CDM group are super-orthogonal to each other.

[0043] In some embodiments, for 5 spatial layers, three DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group. The two DMRS ports in the second CDM group are super-orthogonal to each other, and the two DMRS ports in the second CDM group are not 3GPP Rel-15 DMRS ports (i.e., predetermined DMRS ports).

[0044] In some embodiments, for 5 spatial layers, four DMRS ports are allocated to the first CDM group and one DMRS port is allocated to the second CDM group. The DMRS ports in the second CDM group are using DMRS ports that are not 3GPP Rel-15 DMRS ports (i.e., predetermined DMRS ports).

[0045] In some embodiments, for 6 spatial layers, four DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group. The two DMRS ports in the second CDM group are super-orthogonal to each other.

[0046] In some embodiments, for 6 spatial layers, four DMRS ports are allocated to a first CDM group and two DMRS ports are allocated to a second CDM group. The two DMRS ports in the second CDM group are super-orthogonal to each other, and the two DMRS ports in the second CDM group are not 3GPP Rel-15 DMRS ports (i.e., predetermined DMRS ports).

[0047] In some embodiments, for 6 spatial layers (for DMRS type II), two DMRS ports are allocated to a first CDM group, two DMRS ports are allocated to a second CDM group, and two DMRS ports are allocated to a third CDM group. The two DMRS ports in each CDM group are super-orthogonal to each other, and the two DMRS ports in the third CDM group are not 3GPP Rel-15 DMRS ports (i.e., predetermined DMRS ports).

[0048] In some embodiments, for 6 spatial layers (for DMRS type II), two DMRS ports are allocated to a first CDM group, two DMRS ports are allocated to a second CDM group, and two DMRS ports are allocated to a third CDM group. The two DMRS ports in each CDM group are super-orthogonal to each other, and the two DMRS ports in the second CDM group and the two DMRS ports in the third CDM group are not 3GPP Rel-15 DMRS ports (i.e., predetermined DMRS ports).

[0049] In some embodiments, for 6 spatial layers (for DMRS type II), two DMRS ports are allocated to the first CDM group, two DMRS ports are allocated to the second CDM group, and two DMRS ports are allocated to the third CDM group. The two DMRS ports in each CDM group are super-orthogonal to each other and are not 3GPP Rel-15 DMRS ports (i.e., predetermined DMRS ports).

[0050] In some embodiments, for dual DMRS symbols, the number of CDM groups is minimized by utilizing frequency domain orthogonal cover codes (FD-OCC) combined with time domain orthogonal cover codes (TD-OCC).

[0051] Some embodiments provide an antenna port (DMRS port) indicator table. The antenna port indicator table can be designed to have a predetermined robustness (e.g., good robustness) against delay spread and a predetermined orthogonality (e.g., good orthogonality) with respect to legacy DMRS ports. This, in turn, can increase uplink (UL) multi-user multiple input multiple output (MU-MIMO) capacity because more WDs can be served simultaneously while still maintaining a predetermined DMRS channel estimation quality.

[0052] According to one aspect, a wireless device (WD) configured to communicate with a network node is provided. The WD is configured to allocate demodulation reference signal (DMRS) ports for physical uplink shared channel (PUSCH) transmissions. The WD is configured to receive an indication of a codepoint of an antenna port field for scheduling PUSCH, the codepoint indicating an allocation of DMRS ports to at least a first code division multiplexing (CDM) group, the indication indicating at least five PUSCH layers. The WD is configured to determine a DMRS port configuration based on the codepoint, and to transmit reference signaling according to the determined DMRS port configuration.

[0053] According to this aspect, in some embodiments, the allocation of DMRS ports is configured to maximize the number of mutually super-orthogonal DMRS ports allocated to the first CDM group. In some embodiments, all DMRS ports to be allocated are allocated to the first CDM group using two time division orthogonal cover codes (TD-OCCs). In some embodiments, the allocation of DMRS ports is configured to maximize the number of mutually super-orthogonal DMRS ports in the second CDM group. In some embodiments, when the number of spatial layers is five, three DMRS ports are allocated to the first CDM group, and two DMRS ports are allocated to the second CDM group, with the two DMRS ports in the second CDM group being mutually super-orthogonal. In some embodiments, when the number of spatial layers is six, four DMRS ports are allocated to the first CDM group, and two DMRS ports are allocated to the second CDM group, with the two DMRS ports in the second CDM group being mutually super-orthogonal. In some embodiments, when the number of spatial layers is six, two DMRS ports are allocated to the first CDM group, two DMRS ports are allocated to the second CDM group, and two DMRS ports are allocated to the third CDM group, with the two DMRS ports in each CDM group being mutually super-orthogonal. In some embodiments, for dual DMRS symbols, the number of CDM groups is minimized by utilizing a frequency domain orthogonal cover code FD-OCC combined with a time domain orthogonal cover code TD-OCC.

[0054] According to another aspect, a method is provided in a wireless device (WD) configured to communicate with a network node. The WD is configured to allocate demodulation reference signal (DMRS) ports for physical uplink shared channel (PUSCH) transmissions. The method includes receiving an indication of a codepoint of an antenna port field for scheduling PUSCH, the codepoint indicating an allocation of DMRS ports to at least a first code division multiplexing (CDM) group, the indication indicating at least five PUSCH layers. The method includes determining a DMRS port configuration based on the codepoint. The method also includes transmitting reference signaling based on the determined DMRS port configuration.

[0055] According to this aspect, in some embodiments, the allocation of DMRS ports is configured to maximize the number of mutually super-orthogonal DMRS ports allocated to the first CDM group. In some embodiments, all DMRS ports to be allocated are allocated to the first CDM group using two time division orthogonal cover codes (TD-OCCs). In some embodiments, the allocation of DMRS ports is configured to maximize the number of mutually super-orthogonal DMRS ports in the second CDM group. In some embodiments, when the number of spatial layers is five, three DMRS ports are allocated to the first CDM group, and two DMRS ports are allocated to the second CDM group, with the two DMRS ports in the second CDM group being mutually super-orthogonal. In some embodiments, when the number of spatial layers is six, four DMRS ports are allocated to the first CDM group, and two DMRS ports are allocated to the second CDM group, with the two DMRS ports in the second CDM group being mutually super-orthogonal. In some embodiments, when the number of spatial layers is six, two DMRS ports are allocated to the first CDM group, two DMRS ports are allocated to the second CDM group, and two DMRS ports are allocated to the third CDM group, with the two DMRS ports in each CDM group being mutually super-orthogonal. In some embodiments, for dual DMRS symbols, the number of CDM groups is minimized by utilizing a frequency domain orthogonal cover code FD-OCC combined with a time domain orthogonal cover code TD-OCC.

[0056] According to yet another aspect, a network node configured to communicate with a wireless device (WD) is provided. The WD is configured to allocate demodulation reference signal (DMRS) ports for physical uplink shared channel (PUSCH) transmissions. The network node is configured to transmit an indication of a codepoint of an antenna port field for scheduling PUSCH, the codepoint indicating an allocation of DMRS ports to at least a first code division multiplexing (CDM) group, the indication indicating at least five PUSCH layers. The network node is configured to receive signaling using one or more of the allocated DMRS ports, as indicated by the codepoint of the antenna port field.

[0057] According to this aspect, in some embodiments, the allocation of DMRS ports is configured to maximize the number of mutually super-orthogonal DMRS ports allocated to the first CDM group. In some embodiments, all DMRS ports to be allocated are allocated to the first CDM group using two time division orthogonal cover codes (TD-OCCs). In some embodiments, the allocation of DMRS ports is configured to maximize the number of mutually super-orthogonal DMRS ports in the second CDM group. In some embodiments, when the number of spatial layers is five, three DMRS ports are allocated to the first CDM group, and two DMRS ports are allocated to the second CDM group, with the two DMRS ports in the second CDM group being mutually super-orthogonal. In some embodiments, when the number of spatial layers is six, four DMRS ports are allocated to the first CDM group, and two DMRS ports are allocated to the second CDM group, with the two DMRS ports in the second CDM group being mutually super-orthogonal. In some embodiments, when the number of spatial layers is six, two DMRS ports are allocated to the first CDM group, two DMRS ports are allocated to the second CDM group, and two DMRS ports are allocated to the third CDM group, with the two DMRS ports in each CDM group being mutually super-orthogonal. In some embodiments, for dual DMRS symbols, the number of CDM groups is minimized by utilizing a frequency domain orthogonal cover code FD-OCC combined with a time domain orthogonal cover code TD-OCC.

[0058] According to another aspect, a method is provided in a network node configured to communicate with a wireless device (WD). The WD is configured to allocate demodulation reference signal (DMRS) ports for physical uplink shared channel (PUSCH) transmissions. The method includes transmitting an indication of a codepoint of an antenna port field for scheduling PUSCH, the codepoint indicating an allocation of DMRS ports to at least a first code division multiplexing (CDM) group, the indication indicating at least five PUSCH layers. The method includes receiving signaling using one or more of the allocated DMRS ports in accordance with the indication of the codepoint of the antenna port field.

[0059] According to this aspect, in some embodiments, the allocation of DMRS ports is configured to maximize the number of mutually super-orthogonal DMRS ports allocated to the first CDM group. In some embodiments, all DMRS ports to be allocated are allocated to the first CDM group using two time division orthogonal cover codes TD-OCC. In some embodiments, the allocation of DMRS ports is configured to maximize the number of mutually super-orthogonal DMRS ports in the second CDM group. In some embodiments, when the number of spatial layers is five, three DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group, the two DMRS ports in the second CDM group being mutually super-orthogonal. In some embodiments, when the number of spatial layers is six, four DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group, the two DMRS ports in the second CDM group being mutually super-orthogonal. In some embodiments, the two DMRS ports allocated to the second group exclude DMRS port types defined by the first wireless communication standard and include DMRS ports defined by a second wireless communication standard, the second wireless communication standard being released after the first wireless communication standard. In some embodiments, when the number of spatial layers is six, two DMRS ports are allocated to the first CDM group, two DMRS ports are allocated to the second CDM group, and two DMRS ports are allocated to the third CDM group, and the two DMRS ports in each CDM group are mutually super-orthogonal. In some embodiments, for dual DMRS symbols, the number of CDM groups is minimized by utilizing a frequency domain orthogonal cover code FD-OCC combined with a time domain orthogonal cover code TD-OCC. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] A more complete understanding of the present embodiments and its attendant advantages and features will be more readily appreciated by referring to the following detailed description considered in conjunction with the accompanying drawings, in which: Figure 1 An example NR time domain structure with 15kHz subcarrier spacing is shown; Figure 2 An example NR physical resource grid is shown; Figure 3 ad show example pre-DM-RSs for configuring type 1 and type 2; Figure 4 An example DM-RS configuration for PDSCH mapping type A is shown; Figure 5 An example DM-RS configuration for PDSCH mapping type B is shown; Figure 6 shows example FD-OCC lengths according to different 3GPP releases; Figure 7is a schematic diagram illustrating an example network architecture of a communication system connected to a host computer via an intermediate network according to the principles of the present disclosure; Figure 8 is a block diagram of a host computer communicating with a wireless device via a network node over an at least partially wireless connection according to some embodiments of the present disclosure; Figure 9 is a flow chart illustrating an example method implemented in a communication system including a host computer, a network node, and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure; Figure 10 is a flow chart illustrating an example method implemented in a communication system including a host computer, a network node, and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure; Figure 11 is a flowchart illustrating an example method implemented in a communication system including a host computer, a network node, and a wireless device for receiving user data at the host computer from the wireless device according to some embodiments of the present disclosure; Figure 12 is a flow chart illustrating an example method implemented in a communication system including a host computer, a network node, and a wireless device for receiving user data at the host computer according to some embodiments of the present disclosure; Figure 13 is a flow chart of an example process in a wireless device according to some embodiments of the present disclosure; Figure 14 is a flow chart of an example process in a network node according to some embodiments of the present disclosure; Figure 15 is a flow chart of an example process in a wireless device according to some embodiments of the present disclosure; Figure 16 is a flow chart of an example process in a network node according to some embodiments of the present disclosure; Figure 17 shows example DMRS port numbering for DMRS Type 1 using cyclic shift according to some embodiments of the present disclosure; Figure 18 shows example DMRS port numbering for DMRS type 2 using cyclic shift according to some embodiments of the present disclosure; Figure 19 shows example DMRS port numbering for DMRS type 1 with 2 preamble symbols using cyclic shift according to some embodiments of the present disclosure; Figure 20 shows example DMRS port numbering for DMRS type 2 with 2 preamble symbols using cyclic shift according to some embodiments of the present disclosure; Figure 21 shows an example row in an antenna port table for single-symbol DMRS of extended DMRS type 1 and rank 5 according to some embodiments of the present disclosure; Figure 22 shows an example row in an antenna port table for single-symbol DMRS of extended DMRS type 2 and rank 5 according to some embodiments of the present disclosure; Figure 23 shows an example row in an antenna port table for single-symbol DMRS of extended DMRS type 1 and rank 6 according to some embodiments of the present disclosure; Figure 24 shows an example row in an antenna port table for single-symbol DMRS of extended DMRS type 2 and rank 6 according to some embodiments of the present disclosure; and Figure 25 An example additional row of the antenna port table for DMRS type 1 for extended DMRS for PUSCH ranks 5, 6, 7, and 8 is shown (e.g., to increase the number of REs used for PUSCH (assuming SU-MIMO)) in accordance with some embodiments of the present disclosure. DETAILED DESCRIPTION

[0061] Before describing the exemplary embodiments in detail, it should be noted that the embodiments reside primarily in a combination of device components and processing steps related to antenna port entries for more than four layers of PUSCH. Accordingly, conventional symbols have been used to represent components in the figures where appropriate, and only those specific details relevant to understanding these embodiments are shown to avoid obscuring the disclosure in details that would be readily apparent to one of ordinary skill in the art having the benefit of the description herein. Similar reference numerals refer to similar elements throughout the description.

[0062] As used herein, relational terms such as "first" and "second", "top" and "bottom", etc. may be used only to distinguish one entity or element from another entity or element, and do not necessarily require or imply any physical or logical relationship or order between such entities or elements. The terms used herein are only for the purpose of describing specific embodiments and are not intended to limit the concepts described herein. As used herein, unless the context clearly indicates otherwise, the singular forms "a", "a", and "the" are intended to include the plural forms as well. It will be further understood that the terms "include" and / or "comprising", when used herein, specify the presence of the described features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof.

[0063] In the embodiments described herein, connection terms such as "in communication with..." may be used to indicate electrical or data communication, which may be achieved through, for example, physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling, or optical signaling. Those skilled in the art will appreciate that the various components may interoperate and that modifications and variations in achieving electrical and data communication are possible.

[0064] In some embodiments described herein, terms such as "coupled," "connected," and the like may be used herein to indicate a connection (although not necessarily a direct connection) and may include wired and / or wireless connections.

[0065] The term "network node" as used herein may be any type of network node included in a radio network, which may further include any of the following: a base station (BS), a radio base station, a base transceiver station (BTS), a base station controller (BSC), a radio network controller (RNC), a gNodeB (gNB), an evolved NodeB (eNB or eNodeB), a NodeB, a multi-standard radio (MSR) radio node (such as an MSR BS), a multi-cell / multicast coordination entity (MCE), an integrated access and backhaul (IAB) node, a relay node, a donor node that controls the relay, a radio access point (AP), a transmission point, a transmission node, a remote radio unit (RRU) remote radio head (RRH), a core network node (e.g., a mobility management entity (MME), a self-organizing network (SON) node, a coordination node, a positioning node, an MDT node, etc.), an external node (e.g., a third-party node, a node outside the current network), a node in a distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also include test equipment.As used herein, the term "radio node" may also be used to refer to a wireless device (WD), such as a wireless device (WD) or a radio network node.

[0066] In some embodiments, the non-limiting terms wireless device (WD) or user equipment (UE) are used interchangeably. A WD herein may be any type of wireless device capable of communicating with a network node or another WD via radio signals, such as a wireless device (WD). A WD may also be a radio communication device, a target device, a device-to-device (D2D) WD, a machine-type WD, or a WD capable of machine-to-machine communication (M2M), a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet, a mobile terminal, a smartphone, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a customer premises equipment (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IoT) device, etc.

[0067] Moreover, in some embodiments, the general term "radio network node" is used. It can be any kind of radio network node, which can include any of the following: base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, multi-cell / multicast coordination entity (MCE), IAB node, relay node, access point, radio access point, remote radio unit (RRU), remote radio head (RRH).

[0068] In some embodiments, the term "table" is used, which may refer to any of a data structure, indication, configuration, assignment, matrix, etc. In some embodiments, a table includes information fields, bit fields, etc., and may be organized, for example, in two dimensions (or, more broadly, N dimensions), such as rows and columns. The table (and / or data structure, indication, configuration, assignment, etc.) may be signaled in one or more network nodes or WD transmissions / messages / etc. and / or may be preconfigured in the network nodes and / or WDs.

[0069] In some embodiments, the term "DMRS" (or DM-RS) is used, which may refer to signaling such as (one or more) reference signals used for demodulation. For example, DMRS may be used to estimate a radio channel and / or beamforming and / or be associated with a resource and / or code division multiplexing (CDM) group. DMRS may be transmitted and / or received in an uplink and / or downlink. DMRS may be associated with and / or correspond to a port (e.g., an antenna port, a physical port, a logical port, etc.). For example, a network node and / or a WD may be configured with one or more antennas, e.g., wherein at least one of the antennas includes a physical / logical port that may be mapped to and / or corresponds to a DMRS port.

[0070] Note that while terminology from one particular wireless system, such as 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be construed to limit the scope of this disclosure to only such systems. Other wireless systems, including but not limited to Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB), and Global System for Mobile Communications (GSM), may also benefit from utilizing the concepts encompassed within this disclosure.

[0071] It is further noted that the functions described herein as being performed by a wireless device or network node may be distributed across multiple wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network nodes and wireless devices described herein are not limited to being performed by a single physical device and may in fact be distributed across several physical devices.

[0072] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that the terms used herein should be interpreted as having a meaning consistent with their meaning in the context of this specification and the related art, and will not be interpreted in an idealized or overly formal sense unless explicitly defined as such herein.

[0073] Referring again to the drawings, in which like reference numerals refer to like elements, Figure 7 , a schematic diagram of a communication system 10 according to an embodiment, such as a 3GPP-type cellular network that can support standards such as LTE and / or NR (5G), is shown. The access network 12 includes a plurality of network nodes 16a, 16b, 16c (collectively, network nodes 16), such as NBs, eNBs, gNBs, or other types of wireless access points, each of which defines a corresponding coverage area 18a, 18b, 18c (collectively, coverage area 18). Each network node 16a, 16b, 16c is connectable to the core network 14 via a wired or wireless connection 20. A first wireless device (WD) 22a located in the coverage area 18a is configured to be wirelessly connected to or paged by the corresponding network node 16a. A second WD 22b in the coverage area 18b is wirelessly connected to the corresponding network node 16b. Although multiple WDs 22a, 22b (collectively referred to as wireless devices 22) are shown in this example, the disclosed embodiments are equally applicable to situations where only a single WD is in the coverage area or a single WD is connecting to a corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.

[0074] Furthermore, it is contemplated that the WD 22 may communicate simultaneously with more than one network node 16 and more than one type of network node 16 and / or be configured to communicate separately with these network nodes 16. For example, the WD 22 may have dual connectivity with a network node 16 that supports LTE and the same or different network nodes 16 that support NR. For example, the WD 22 may communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0075] The communication system 10 itself may be connected to a host computer 24, which may be implemented in hardware and / or software on a stand-alone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 24 may be owned or controlled by a service provider, or may be operated by or on behalf of a service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24, or may extend via an optional intermediate network 30. The intermediate network 30 may be one of a public, private, or managed network, or a combination of more than one of these networks. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may include two or more subnetworks (not shown).

[0076] Figure 7 The communication system as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. This connectivity can be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to use the access network 12, the core network 14, any intermediate networks 30, and possible further infrastructure (not shown) as intermediaries to transfer data and / or signaling via the OTT connection. The OTT connection can be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of the routing of uplink and downlink communications. For example, the network node 16 may not or need not be informed of the past routing of incoming downlink communications with data originating from the host computer 24 to be forwarded (e.g., handed over) to the connected WD 22a. Similarly, the network node 16 does not need to know the future routing of outgoing uplink communications originating from the WD 22a toward the host computer 24.

[0077] The network node 16 is configured to include a NN management unit 32, which is configured to perform any of the steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, such as transmitting an indication of a code point of an antenna port field in downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH), the indication indicating at least one spatial layer; and receiving signaling using one or more allocated DMRS ports based on the indication of the code point of the antenna port field. The wireless device 22 is configured to include a WD management unit 34, which is configured to perform any of the steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, such as receiving an indication of a code point of an antenna port field in downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH), the indication indicating at least one spatial layer; and transmitting signaling using one or more allocated DMRS ports based on the indication of the code point of the antenna port field. The NN management unit 32 may be configured to execute any steps and / or tasks and / or processes and / or methods and / or features of the WD management unit 34. Similarly, the WD management unit 34 may be configured to execute any steps and / or tasks and / or processes and / or methods and / or features of the NN management unit 32.

[0078] Now refer to Figure 8 An example implementation according to an embodiment of the WD 22, network node 16, and host computer 24 discussed in the previous paragraphs is described. In the communication system 10, the host computer 24 includes hardware (HW) 38, which includes a communication interface 40, which is configured to establish and maintain a wired or wireless connection to the interface with different communication devices of the communication system 10. The host computer 24 further includes processing circuitry 42, which may have storage and / or processing capabilities. The processing circuitry 42 may include a processor 44 and a memory 46. In particular, in addition to or in place of a processor (such as a central processing unit) and a memory, the processing circuitry 42 may include an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) suitable for executing instructions. The processor 44 may be configured to access (e.g., write to and / or read from) a memory 46, which may include any type of volatile and / or non-volatile memory, such as cache and / or buffer memory and / or RAM (random access memory) and / or ROM (read-only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory).

[0079] Processing circuitry 42 may be configured to control any of the methods and / or processes described herein and / or cause such methods and / or processes to be performed, for example, by host computer 24. Processor 44 corresponds to one or more processors 44 for performing the functions of host computer 24 described herein. Host computer 24 includes memory 46 configured to store data, programming software code, and / or other information described herein. In some embodiments, software 48 and / or host application 50 may include instructions that, when executed by processor 44 and / or processing circuitry 42, cause processor 44 and / or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with host computer 24.

[0080] The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide services to a remote user, such as a WD 22 connected via an OTT connection 52 terminated at the WD 22 and the host computer 24. During the provision of services to the remote user, the host application 50 may provide user data, which may be transmitted using the OTT connection 52. "User data" may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured to provide control and functionality to a service provider and may be operated by or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and / or receive from the network node 16 and / or the wireless device 22. The processing circuitry 42 of the host computer 24 may include a host management unit 54 configured to enable the service provider to perform any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, e.g., observing / monitoring / controlling / transmitting to / receiving from the network nodes 16 and / or wireless devices 22.

[0081] Communication system 10 further includes a network node 16, which is disposed within communication system 10 and includes hardware 58 that enables it to communicate with host computer 24 and with WD 22. Hardware 58 may include a communication interface 60 for establishing and maintaining wired or wireless connections interfacing with various communication devices of communication system 10, and a radio interface 62 for establishing and maintaining at least wireless connections 64 with WD 22 located within coverage area 18 served by network node 16. Radio interface 62 may include one or more antennas 76. Radio interface 62 (and / or antenna 76 (which may include ports such as DMRS ports)) may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. Communication interface 60 may be configured to facilitate connection 66 to host computer 24. Connection 66 may be direct, or it may pass through core network 14 of communication system 10 and / or through one or more intermediate networks 30 external to communication system 10.

[0082] In the illustrated embodiment, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or in place of a processor (such as a central processing unit) and memory, the processing circuitry 68 may include an integrated circuit for processing and / or control, such as, for example, one or more processors and / or processor cores and / or FPGAs (field programmable gate arrays) and / or ASICs (application-specific integrated circuits / circuit modules) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and / or read from) the memory 72, which may include any type of volatile and / or non-volatile memory, such as a cache and / or buffer memory and / or RAM (random access memory) and / or ROM (read-only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory).

[0083] Thus, network node 16 further includes software 74, which is stored internally, for example, in memory 72, or in external memory (e.g., a database, storage array, network storage device, etc.) accessible to network node 16 via an external connection. Software 74 may be executable by processing circuitry 68. Processing circuitry 68 may be configured to control any of the methods and / or processes described herein and / or cause such methods and / or processes to be performed, for example, by network node 16. Processor 70 corresponds to one or more processors 70 configured to perform the network node 16 functionality described herein. Memory 72 is configured to store data, programming software code, and / or other information described herein. In some embodiments, software 74 may include instructions that, when executed by processor 70 and / or processing circuitry 68, cause processor 70 and / or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, the processing circuit 68 of the network node 16 may include a NN management unit 32, which is configured to perform any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, for example, transmitting an indication of a code point of an antenna port field in downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH), the indication indicating at least one spatial layer; and receiving signaling using one or more allocated DMRS ports based on the indication of the code point of the antenna port field.

[0084] The communication system 10 further includes the already mentioned WD 22. The WD 22 may have hardware 80, which may include a radio interface 82 configured to establish and maintain a wireless connection 64 with a network node 16 serving the coverage area 18 in which the WD 22 is currently located. The radio interface 82 includes one or more antennas 83. The radio interface 82 (and / or the antenna 83 (which may include a port such as a DMRS port)) may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0085] The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and a memory 88. In particular, in addition to or in place of a processor (such as a central processing unit) and memory, the processing circuitry 84 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and / or read from) the memory 88, which may include any type of volatile and / or non-volatile memory, such as a cache and / or buffer memory and / or RAM (random access memory) and / or ROM (read-only memory) and / or optical storage and / or EPROM (erasable programmable read-only memory).

[0086] Therefore, WD 22 may further include software 90, which is stored in, for example, memory 88 at WD 22, or in an external memory accessible to WD 22 (e.g., a database, storage array, network storage device, etc.). The software 90 may be executable by the processing circuit 84. The software 90 may include a client application 92. The client application 92 may be operable to provide services to human or non-human users via WD 22 with the support of the host computer 24. In the host computer 24, the executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminated at the WD 22 and the host computer 24. During the provision of services to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transmit both the request data and the user data. The client application 92 may interact with the user to generate the user data it provides.

[0087] The processing circuit 84 may be configured to control any of the methods and / or processes described herein, and / or cause such methods and / or processes to be performed, for example, by the WD 22. The processor 86 corresponds to one or more processors 86 for performing the WD 22 functions described herein. The WD 22 includes a memory 88 that is configured to store data, programming software code, and / or other information described herein. In some embodiments, the software 90 and / or client application 92 may include instructions that, when executed by the processor 86 and / or the processing circuit 84, cause the processor 86 and / or the processing circuit 84 to perform the processes described herein with respect to the WD 22. For example, the processing circuit 84 of the wireless device 22 may include a WD management unit 34, which is configured to perform any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, for example, receiving an indication of a code point of an antenna port field in downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH), the indication indicating at least one spatial layer; and using one or more allocated DMRS ports to transmit signaling according to the indication of the code point of the antenna port field.

[0088] In some embodiments, the internal workings of network node 16, WD 22, and host computer 24 may be as follows: Figure 8 As shown in , and independently, the surrounding network topology can be Figure 7 Like that.

[0089] exist Figure 8 In FIG, OTT connection 52 has been abstractly drawn to illustrate communication between host computer 24 and wireless device 22 via network node 16, without explicitly mentioning any intermediate devices and the exact routing of messages through these devices. The network infrastructure can determine the routing, which can be configured to be hidden from WD 22 or the service provider operating host computer 24, or both. While OTT connection 52 is active, the network infrastructure can make further decisions (e.g., based on load balancing considerations or network reconfiguration) through which it dynamically changes the routing.

[0090] The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of over-the-top (OTT) services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the final leg. More specifically, the teachings of some of these embodiments may improve data rates, latency, and / or power consumption, thereby providing benefits such as reduced user wait time, relaxed file size restrictions, better responsiveness, and extended battery life.

[0091] In some embodiments, 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 further be provided for reconfiguring the OTT connection 52 between the host computer 24 and the WD 22 in response to changes in measurement results. The measurement process and / or network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24, in the software 90 of the WD 22, or in both. In embodiments, sensors (not shown) may be deployed in or associated with the communication device through which the OTT connection 52 passes; the sensors may participate in the measurement process by supplying values for the monitored quantities exemplified above or for other physical quantities (based on which the software 48, 90 may calculate or estimate the monitored quantities). Reconfiguration of the OTT connection 52 may include message formats, retransmission settings, preferred routing, and the like; reconfiguration need not affect the network node 16 and may be performed without the network node 16's knowledge or perception. Some such processes and functionality may be known and practiced in the art. In some embodiments, the measurements may involve proprietary WD signaling that facilitates the host computer 24's measurement of throughput, propagation time, latency, etc. In some embodiments, the measurements may be achieved because the software 48, 90 causes messages (particularly empty or 'dummy' messages) to be transmitted using the OTT connection 52 while it monitors propagation time, errors, etc.

[0092] Thus, in some embodiments, host computer 24 includes processing circuitry 42 configured to provide user data and communication interface 40 configured to forward the user data to a cellular network for transmission to WD 22. In some embodiments, cellular network also includes a network node 16 having a radio interface 62. In some embodiments, network node 16 is configured and / or processing circuitry 68 of network node 16 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating transmissions to WD 22, and / or preparing / terminating / maintaining / supporting / terminating receipt of transmissions from WD 22.

[0093] In some embodiments, host computer 24 includes processing circuitry 42 and communication interface 40 configured to receive user data originating from transmissions from WD 22 to network node 16. In some embodiments, WD 22 is configured to, and / or includes radio interface 82 and / or processing circuitry 84 and is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / terminating transmissions to network node 16, and / or preparing / terminating / maintaining / supporting / terminating receipt of transmissions from network node 16.

[0094] Although Figure 7 and Figure 8Various "units," such as NN management unit 32 and WD management unit 34, are shown as being within respective processors, but it is contemplated that these units may be implemented such that portions of the units are stored in corresponding memories within the processing circuitry. In other words, these units may be implemented in hardware, or in a combination of software and hardware within the processing circuitry.

[0095] Figure 9 is a diagram showing a communication system (such as, for example, Figure 7 and Figure 8 The communication system may include a host computer 24, a network node 16, and a WD 22, which may be a reference Figure 8 Those described herein. In a first step of the method, the host computer 24 provides user data (block S100). In an optional sub-step of the first step, the host computer 24 provides the user data by executing a host application (such as, for example, the host application 50) (block S102). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (block S104). In an optional third step, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 transmits the user data carried in the transmission initiated by the host computer 24 to the WD 22 (block S106). In an optional fourth step, the WD 22 executes a client application (such as, for example, the client application 92) associated with the host application 50 executed by the host computer 24 (block S108).

[0096] Figure 10 is a diagram showing a communication system (such as, for example, Figure 7 The communication system may include a host computer 24, a network node 16, and a WD 22, which may be a reference Figure 7 and Figure 8 Those described herein. In a first step of the method, host computer 24 provides user data (block S110). In an optional sub-step (not shown), host computer 24 provides the user data by executing a host application (such as, for example, host application 50). In a second step, host computer 24 initiates a transmission carrying the user data to WD 22 (block S112). According to the teachings of the embodiments described throughout this disclosure, the transmission may pass through network node 16. In an optional third step, WD 22 receives the user data carried in the transmission (block S114).

[0097] Figure 11 is a diagram showing a communication system (such as, for example, Figure 7The communication system may include a host computer 24, a network node 16, and a WD 22, which may be a reference Figure 7 and Figure 8 Those described. In an optional first step of the method, WD 22 receives input data provided by host computer 24 (box S116). In an optional sub-step of the first step, WD 22 executes client application 92, which responds to the input data received from host computer 24 and provides user data (box S118). Additionally or alternatively, in an optional second step, WD 22 provides user data (box S120). In an optional sub-step of the second step, WD provides user data by executing a client application (such as, for example, client application 92) (box S122). During the provision of user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data has been provided, in an optional third sub-step, WD 22 may initiate the transmission of the user data to host computer 24 (box S124). In a fourth step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, host computer 24 receives the user data transmitted from WD 22 (box S126).

[0098] Figure 12 is a diagram showing a communication system (such as, for example, Figure 7 The communication system may include a host computer 24, a network node 16, and a WD 22, which may be a reference Figure 7 and Figure 8 In an optional first step of the method, network node 16 receives user data from WD 22 in accordance with the teachings of the embodiments described throughout this disclosure (block S128). In an optional second step, network node 16 initiates a transmission of the received user data to host computer 24 (block S130). In a third step, host computer 24 receives the user data carried in the transmission initiated by network node 16 (block S132).

[0099] Figure 13is a flow chart of an example process in the wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of the wireless device 22, such as by one or more of the processing circuitry 84 (including the WD management unit 34), the processor 86, the radio interface 82, and / or the communication interface 60. The wireless device 22 is configured to receive (block S134) an indication of a code point of an antenna port field in downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH), the indication indicating at least one spatial layer; and transmit (cause transmission) (block S136) signaling using one or more allocated DMRS ports in accordance with the indication of the code point of the antenna port field.

[0100] In some embodiments, when the at least one spatial layer includes five spatial layers, three DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group. The two DMRS ports in the second CDM group are super-orthogonal to each other.

[0101] In some embodiments, the two DMRS ports in the second CDM group are not predetermined DMRS ports.

[0102] In some embodiments, when the at least one spatial layer includes five spatial layers, four DMRS ports are allocated to the first CDM group and one DMRS port is allocated to the second CDM group. The DMRS ports in the second CDM group are not predetermined DMRS ports.

[0103] In some embodiments, when the at least one spatial layer includes six spatial layers, four DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group. The two DMRS ports in the second CDM group are super-orthogonal to each other.

[0104] In some embodiments, the two DMRS ports in the second CDM group are not predetermined DMRS ports.

[0105] In some embodiments, when the at least one spatial layer includes six spatial layers for DMRS Type II, two DMRS ports are allocated to a first CDM group, two DMRS ports are allocated to a second CDM group, and two DMRS ports are allocated to a third CDM group. The two DMRS ports in each CDM group are super-orthogonal to each other, and each of the two DMRS ports in the third CDM group is not a predetermined DMRS port.

[0106] In some embodiments, when at least one spatial layer includes six spatial layers for DMRS Type II, two DMRS ports are allocated to a first CDM group, two DMRS ports are allocated to a second CDM group, and two DMRS ports are allocated to a third CDM group. The two DMRS ports in each CDM group are super-orthogonal to each other. Each of the two DMRS ports in the second CDM group and each of the two DMRS ports in the third CDM group are not predetermined DMRS ports.

[0107] In some embodiments, when at least one spatial layer includes six spatial layers for DMRS Type II, two DMRS ports are allocated to a first CDM group, two DMRS ports are allocated to a second CDM group, and two DMRS ports are allocated to a third CDM group. The two DMRS ports in each CDM group are super-orthogonal to each other. The two DMRS ports in each CDM group are super-orthogonal to each other and are not predetermined DMRS ports.

[0108] In some embodiments, for dual DMRS symbols, the number of CDM groups is minimized by utilizing frequency domain orthogonal cover codes (FD-OCC) combined with time domain orthogonal cover codes (TD-OCC).

[0109] Figure 14 is a flow diagram of an example process in the network node 16. One or more blocks described herein may be performed by one or more elements of the network node 16, such as by one or more of the processing circuitry 68 (including the NN management unit 32), the processor 70, the radio interface 62, and / or the communication interface 60. The network node 16 is configured to transmit (cause to be transmitted) (block S138) in downlink control information DCI for scheduling a physical uplink shared channel, PUSCH, an indication of a code point of an antenna port field, the indication specifying at least one spatial layer; and receive (block S140) signaling using one or more allocated DMRS ports according to the indication of the code point of the antenna port field.

[0110] In some embodiments, when the at least one spatial layer includes five spatial layers, three DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group. The two DMRS ports in the second CDM group are super-orthogonal to each other.

[0111] In some embodiments, the two DMRS ports in the second CDM group are not predetermined DMRS ports.

[0112] In some embodiments, when the at least one spatial layer includes five spatial layers, four DMRS ports are allocated to the first CDM group and one DMRS port is allocated to the second CDM group. The DMRS ports in the second CDM group are not predetermined DMRS ports.

[0113] In some embodiments, when the at least one spatial layer includes six spatial layers, four DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group. The two DMRS ports in the second CDM group are super-orthogonal to each other.

[0114] In some embodiments, the two DMRS ports in the second CDM group are not predetermined DMRS ports.

[0115] In some embodiments, when the at least one spatial layer includes six spatial layers for DMRS Type II, two DMRS ports are allocated to a first CDM group, two DMRS ports are allocated to a second CDM group, and two DMRS ports are allocated to a third CDM group. The two DMRS ports in each CDM group are super-orthogonal to each other, and each of the two DMRS ports in the third CDM group is not a predetermined DMRS port.

[0116] In some embodiments, when at least one spatial layer includes six spatial layers for DMRS Type II, two DMRS ports are allocated to a first CDM group, two DMRS ports are allocated to a second CDM group, and two DMRS ports are allocated to a third CDM group. The two DMRS ports in each CDM group are super-orthogonal to each other. Each of the two DMRS ports in the second CDM group and each of the two DMRS ports in the third CDM group are not predetermined DMRS ports.

[0117] In some embodiments, when at least one spatial layer includes six spatial layers for DMRS Type II, two DMRS ports are allocated to a first CDM group, two DMRS ports are allocated to a second CDM group, and two DMRS ports are allocated to a third CDM group. The two DMRS ports in each CDM group are super-orthogonal to each other. The two DMRS ports in each CDM group are super-orthogonal to each other and are not predetermined DMRS ports.

[0118] In some embodiments, for dual DMRS symbols, the number of CDM groups is minimized by utilizing frequency domain orthogonal cover codes (FD-OCC) combined with time domain orthogonal cover codes (TD-OCC).

[0119] Figure 15is a flow chart of an example process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of the wireless device 22, such as by one or more of the processing circuitry 84 (including the WD management unit 34), the processor 86, the radio interface 82, and / or the communication interface 60. The wireless device 22 is configured to receive an indication of a code point of an antenna port field for scheduling a PUSCH, the code point indicating an allocation of a DMRS port to at least a first code division multiplexing (CDM) group, the indication indicating at least five PUSCH layers (block S142). The method includes determining a DMRS port configuration based on the code point (block S144). The method also includes transmitting reference signaling according to the determined DMRS port configuration (block S146).

[0120] According to this aspect, in some embodiments, the allocation of DMRS ports is configured to maximize the number of mutually super-orthogonal DMRS ports allocated to the first CDM group. In some embodiments, all DMRS ports to be allocated are allocated to the first CDM group using two time division orthogonal cover codes (TD-OCCs). In some embodiments, the allocation of DMRS ports is configured to maximize the number of mutually super-orthogonal DMRS ports in the second CDM group. In some embodiments, when the number of spatial layers is five, three DMRS ports are allocated to the first CDM group, and two DMRS ports are allocated to the second CDM group, with the two DMRS ports in the second CDM group being mutually super-orthogonal. In some embodiments, when the number of spatial layers is six, four DMRS ports are allocated to the first CDM group, and two DMRS ports are allocated to the second CDM group, with the two DMRS ports in the second CDM group being mutually super-orthogonal. In some embodiments, when the number of spatial layers is six, two DMRS ports are allocated to the first CDM group, two DMRS ports are allocated to the second CDM group, and two DMRS ports are allocated to the third CDM group, with the two DMRS ports in each CDM group being mutually super-orthogonal. In some embodiments, for dual DMRS symbols, the number of CDM groups is minimized by utilizing a frequency domain orthogonal cover code FD-OCC combined with a time domain orthogonal cover code TD-OCC.

[0121] Figure 16is a flow chart of an example process in the network node 16. One or more blocks described herein may be performed by one or more elements of the network node 16, such as by one or more of the processing circuitry 68 (including the NN management unit 32), the processor 70, the radio interface 62, and / or the communication interface 60. The network node 16 is configured to transmit an indication of a code point of an antenna port field for scheduling a PUSCH, the code point indicating an allocation of a DMRS port to at least a first code division multiplexing (CDM) group, the indication indicating at least five PUSCH layers (block S148). The method includes receiving signaling using one or more of the allocated DMRS ports in accordance with the indication of the code point of the antenna port field (block S150).

[0122] According to this aspect, in some embodiments, the allocation of DMRS ports is configured to maximize the number of mutually super-orthogonal DMRS ports allocated to the first CDM group. In some embodiments, all DMRS ports to be allocated are allocated to the first CDM group using two time division orthogonal cover codes TD-OCC. In some embodiments, the allocation of DMRS ports is configured to maximize the number of mutually super-orthogonal DMRS ports in the second CDM group. In some embodiments, when the number of spatial layers is five, three DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group, the two DMRS ports in the second CDM group being mutually super-orthogonal. In some embodiments, when the number of spatial layers is six, four DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group, the two DMRS ports in the second CDM group being mutually super-orthogonal. In some embodiments, the two DMRS ports allocated to the second group exclude DMRS port types defined by the first wireless communication standard and include DMRS ports defined by a second wireless communication standard, the second wireless communication standard being released after the first wireless communication standard. In some embodiments, when the number of spatial layers is six, two DMRS ports are allocated to the first CDM group, two DMRS ports are allocated to the second CDM group, and two DMRS ports are allocated to the third CDM group, and the two DMRS ports in each CDM group are mutually super-orthogonal. In some embodiments, for dual DMRS symbols, the number of CDM groups is minimized by utilizing a frequency domain orthogonal cover code FD-OCC combined with a time domain orthogonal cover code TD-OCC.

[0123] Although WD 22 has been described as being configured to receive an indication of a code point of an antenna port field in DCI for scheduling PUSCH and to transmit signaling using one or more allocated DMRS ports according to the indication of the code point of the antenna port field, WD 22 is not limited thereto and may be configured to perform one or more of the functions described with respect to network node 16. For example, WD 22 may be configured to transmit an indication and to receive signaling. Similarly, network node 16 may be configured to perform one or more of the functions described with respect to WD 22, for example, to receive an indication; and / or to transmit signaling.

[0124] The general process flow of the arrangements of the present disclosure has been described and examples of hardware and software arrangements for implementing the processes and functions of the present disclosure have been provided. The following sections provide details and examples of arrangements for determining antenna port entries for PUSCH with more than four layers.

[0125] One or more of the network node functions described below may be performed by one or more of processing circuitry 68, processor 70, NN management unit 32, etc. One or more of the wireless device functions described below may be performed by one or more of processing circuitry 84, processor 86, WD management unit 34, etc.

[0126] Definition: If two orthogonal vectors and are orthogonal on every K sequence parts of length N’ < N (where N = N’ * K), that is, then the vectors v1 and v2 are called super-orthogonal.

[0127] For example, the vectors of the orthogonal cover codes [1 1 1 1] and [1 -1 1 -1] of length 4 are super-orthogonal because they are also orthogonal on the partial length 2.

[0128] Utilize the property of super-orthogonality between some DMRS ports and the relationship with other (e.g., conventional 3GPP Rel-15) DMRS ports. In the DMRS port index table 9, for eType1, the first 8 rows (ports) use the same FD-OCC (and TD-OCC) as the 3GPP Rel-15 conventional type 1 table. In the following description, these ports (p0 - p7 for PUSCH and p1000 - p1007 for PDSCH) may be referred to as 3GPP Rel-15 type 1 ports. Similarly, for table 10 eType2, the first 12 ports may use the same FD-OCC as the 3GPP Rel-15 conventional type 2 table. These ports (p0 - p11 for PUSCH and p1000 - p1011 for PDSCH) may be referred to as 3GPP Rel-15 type 2 ports.

[0129] For receivers that perform channel estimation using multiple DMRS ports (e.g., rank 2 reception of 2 ports), it may be beneficial to use super-orthogonal DMRS ports for both layers compared to using "only" orthogonal ports.

[0130] More specifically, if a delay-domain channel estimation algorithm is used, a domain transform (such as DFT) can be used to receive the DMRS. Compared to two non-super-orthogonal ports, the two super-orthogonal ports have a larger sample (i.e., time) separation after the transform. This is a property that is at least relevant when there is delay in the channel (the delay introduces cross-interference between the two DMRS ports). For example, to maximize robustness against channel delays, super-orthogonal DMRS ports can be used, or equivalently, the cyclic shift of the DMRS port sequence in the time domain can be maximized.

[0131] Alternatively, if a frequency-domain channel estimation algorithm is used, the shorter sequence length N' that achieves orthogonality between super-orthogonal ports means that the channel estimator can operate on N' samples at a time (e.g., instead of N>N' samples), making the system less susceptible to delay spread / frequency selectivity. Improved channel estimation performance can increase user throughput, especially for higher-order modulation and higher code rates.

[0132] The following principles may form the basis for creating an antenna port indication table (PUSCH DMRS ports) for UL transmission: -When possible, the DMRS ports assigned to WD 22 can use super-orthogonal ports; - DMRS ports assigned to several WDs 22 may be orthogonal to legacy DMRS ports, so that several legacy WDs 22 and several 3GPP Rel-18 WDs 22 may be co-scheduled for UL MU-MIMO; - (for dual-symbol DMRS) use as few CDM groups as possible, e.g. to allow PUSCH rate matching around DMRS subcarriers.

[0133] Port numbers for DMRS eType 1 and eType 2

[0134] In some embodiments, as Figure 17 As shown in , the following DMRS port number definitions for Type 1 DMRS with a single DMRS symbol for 3GPP Rel-18 WD 22 have been used (e.g., assumed). DMRS port 0 and DMRS port 1 may be mutually super-orthogonal to each other, as may DMRS port 8 and DMRS port 9, DMRS port 2 and DMRS port 3, and DMRS port 10 and DMRS port 11.

[0135] That is, in one or more embodiments, assuming that the same DMRS sequence used for DMRS 3GPP Rel-15 is reused for DMRS 3GPP Rel-18, DMRS ports 0 and 1 may be the same as DMRS ports 0 and 1 in the legacy 3GPP Rel-15 DMRS ports. Furthermore, in some embodiments, for example, assuming that the same DMRS sequence used for DMRS 3GPP Rel-15 / 16 is reused for DMRS 3GPP Rel-18, DMRS ports 2 and 3 may be the same as DMRS ports 2 and 3 in the legacy 3GPP Rel-15 DMRS ports.

[0136] Figure 17 Example DMRS port numbering for DMRS type 1 using cyclic shift is shown. The cyclic shift code can be replaced by a Hadamard code. Figure 18 Example DMRS port numbering for DMRS type 2 using cyclic shift is shown. That is, the corresponding port number for DMRS type 2 is shown. Similar to Figure 17 , the cyclic shift code can be replaced by Hadamard code.

[0137] Figure 19 and Figure 20 Example DMRS port numbering for eType1 and eType2 DMRS with 2 preamble symbols is shown. For each port, 2 vectors may be used, where the first vector shows an example of employing a cyclically shifted FD-OCC code, and the second vector shows a TD-OCC code applied to consecutive DMRS symbols. In some embodiments, for port numbers 8-15, the TD-OCC code may be [1, j] or [1, -j] (e.g., instead of [1 1] and [1 -1] as previously used). More specifically, Figure 19 Example DMRS port numbering for DMRS type 1 with 2 preamble symbols using cyclic shift is shown. Figure 20 Example DMRS port numbering for DMRS type 2 with 2 preamble symbols using cyclic shift is shown. Note that the cyclic shift code can be replaced with a Hadamard code.

[0138] When scheduling a WD 22, the network node 16 (e.g., gNB) indicates in the DCI which antenna (DMRS) ports the WD 22 can use for PUSCH transmission. This indication may point to a row in an antenna port indication table. The scheduler of the network node 16 (e.g., gNB) makes the row selection, for example, by considering channel estimation performance, whether the data is frequency division multiplexed (FDM) and / or time division multiplexed (TDM) with the DMRS, and whether the scheduling is single-user (SU) or MU-MIMO.

[0139] In some embodiments, one aspect of designing the UL antenna port table may be to ensure that simultaneously scheduled DMRS ports are super-orthogonal to each other when received by the network node 16 (e.g., a transmission reception point (TRP) and / or a gNB) in order to minimize inter-DMRS port interference. Therefore, in some embodiments, the antenna port indication table may include rows where the simultaneously scheduled DMRS ports separated by coding (e.g., OCC) within each CDM group are super-orthogonal (for a true TRP-WD channel implementation).

[0140] Detailed embodiment of antenna port indication table for 5 PUSCH layers and maxLength=1

[0141] For example, for rank 5, Figure 21 Some detailed examples for DMRS Type 1 are shown in FIG. More specifically, Figure 21 Example rows in the table of antenna ports for extended 3GPP Rel-18 DMRS type 1 single-symbol DMRS and rank 5 are shown. In the row associated with code point value X, three DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group. In addition, the two DMRS ports in the second CDM group are super-orthogonal to each other. In the row associated with code point value X+1, three DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group. The two DMRS ports in the second CDM group are super-orthogonal to each other, and the two DMRS ports in the second CDM group are not 3GPP Rel-15 DMRS ports (i.e., predetermined DMRS ports). In the row associated with code point value X+2, four DMRS ports are allocated to the first CDM group and one DMRS port is allocated to the second CDM group. The DMRS ports in the second CDM group are not 3GPP Rel-15 DMRS ports.

[0142] For example, for rank 5, Figure 22Some detailed examples for DMRS type 2 are shown in FIG. In the row associated with the code point value X, three DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group. The two DMRS ports in the second CDM group are super-orthogonal to each other. In the row associated with the code point value X+1, three DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group. The two DMRS ports in the second CDM group are super-orthogonal to each other and the two DMRS ports in the second CDM group are not 3GPP Rel-15 DMRS ports. In the row associated with the code point value X+2, four DMRS ports are allocated to the first CDM group and one DMRS port is allocated to the second CDM group. The DMRS ports in the second CDM group are not 3GPP Rel-15 DMRS ports.

[0143] Detailed embodiment of antenna port indication table for 6 PUSCH layers and maxLength=1

[0144] For example, for rank 6, Figure 23 Some detailed examples for DMRS type 1 are shown in FIG. In the row associated with codepoint value X, four DMRS ports are allocated to the first CDM group, and two DMRS ports are allocated to the second CDM group. The two DMRS ports in the second CDM group are super-orthogonal to each other. In the row associated with codepoint value X+1, four DMRS ports are allocated to the first CDM group, and two DMRS ports are allocated to the second CDM group. The two DMRS ports in the second CDM group are super-orthogonal to each other, and the two DMRS ports in the second CDM group are not 3GPP Rel-15 DMRS ports.

[0145] For example, for rank 6, Figure 24Some detailed examples for DMRS type 2 are shown in FIG. In the row associated with the code point value X, four DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group. The two DMRS ports in the second CDM group are super-orthogonal to each other. In the row associated with the code point value X+1, four DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group. The two DMRS ports in the second CDM group are super-orthogonal to each other, and the two DMRS ports in the second CDM group are not 3GPP Rel-15 DMRS ports. In the row associated with the code point value X+2, two DMRS ports are allocated to the first CDM group, two DMRS ports are allocated to the second CDM group, and two DMRS ports are allocated to the third CDM group. The two DMRS ports in each CDM group are super-orthogonal to each other, and the two DMRS ports in the third CDM group are not 3GPP Rel-15 DMRS ports. In the row associated with the code point value X+3, two DMRS ports are assigned to the first CDM group, two DMRS ports are assigned to the second CDM group, and two DMRS ports are assigned to the third CDM group. The two DMRS ports in each CDM group are mutually super-orthogonal, and the two DMRS ports in the second CDM group and the two DMRS ports in the third CDM group are not 3GPP Rel-15 DMRS ports. In the row associated with the code point value X+4, two DMRS ports are assigned to the first CDM group, two DMRS ports are assigned to the second CDM group, and two DMRS ports are assigned to the third CDM group. In some embodiments, the two DMRS ports in each CDM group are mutually super-orthogonal and are not 3GPP Rel-15 DMRS ports.

[0146] Detailed embodiment of the antenna port indication table for maxLength=2

[0147] In some cases, it may be beneficial to allocate the DMRS ports for PUSCH to a single CDM group to maximize the number of REs that can be used for PUSCH transmission. At least one reason for this is that PUSCH (transmitted from the same WD 22 or other co-scheduled WD 22) can be rate-matched around unused REs adjacent to the used CDM group. Therefore, the fewer CDM groups used for WD 22, the more REs can be used for PUSCH (for example, when only a single CDM group is used for DMRS type 1 of WD 22 and there is no co-scheduled WD 22, PUSCH can be allocated to every other subcarrier, while if two CDM groups are allocated to WD 22, no REs in the corresponding DMRS symbol can be used for PUSCH).

[0148] Figure 25 Some additional rows of the antenna port table for DMRS type 1 extending 3GPP Rel-18 DMRS are shown for PUSCH ranks 5, 6, 7, and 8 in order to increase the number of REs used for PUSCH (eg, assuming SU-MIMO).

[0149] Assign DMRS ports in different CDM groups to different codewords

[0150] In some embodiments, for uplink transmissions using two codewords, the DMRS ports assigned to each codeword can belong to the same CDM group. For more than four layers, the DMRS ports in the antenna table can be arranged according to the codeword-to-layer mapping. This may be useful at least when using two WD 22 panels (each panel is used to transmit one codeword).

[0151] For example, if five layers are scheduled for PUSCH, the first two layers and associated DMRS ports are assigned to the first codeword. The remaining three layers and associated DMRS ports are assigned to the second codeword. In this example, the two DMRS ports associated with the first codeword (denoted as DMRS ports {n1, n2}) are in the same CDM group, while the three DMRS ports associated with the second codeword (denoted as DMRS ports {m3, m4, m5}) are in another CDM group. The corresponding configuration in the antenna table is shown below in Table 11. Table 11: Example of DMRS port allocation for two codewords using 5 layers, where DMRS ports {n1, n2} In one CDM group, and DMRS ports {m3, m4, m5} are in another different CDM group

[0152] Table 12 shows an example for 6 layers, 7 layers, and 8 layers, where DMRS ports {nk,k=1, 2, 3, 4} are in one CDM group and DMRS ports {mk,k=1, 2, 3, 4} are in another different CDM group. Table 12: Example of DMRS port allocation for two codewords using more than 5 layers, where DMRS port {n1,n2} are in one CDM group, and DMRS ports {n3,n4,n5} are in another CDM group

[0153] Some embodiments may include one or more of the following:

[0154] Embodiment A1. A wireless device WD configured to communicate with a network node, the WD configured to allocate a demodulation reference signal DMRS port for a physical uplink shared channel PUSCH transmission, allocating the DMRS port to at least one of a first code division multiplexing CDM group and a second CDM group, the WD being scheduled with more than four PUSCH layers and being configured to, and / or including a radio interface and / or processing circuitry and being configured to: receiving an indication of a code point of an antenna port field in downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH), the indication indicating at least one spatial layer; and Signaling is transmitted using one or more allocated DMRS ports according to the indication of the code point of the antenna port field.

[0155] Embodiment A2. The WD of embodiment A1, wherein, when the at least one spatial layer includes five spatial layers, three DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group, the two DMRS ports in the second CDM group being super-orthogonal to each other.

[0156] Embodiment A3. The WD of Embodiment A2, wherein two DMRS ports in the second CDM group are not predetermined DMRS ports.

[0157] Embodiment A4. The WD of embodiment A1, wherein, when the at least one spatial layer includes five spatial layers, four DMRS ports are allocated to the first CDM group, one DMRS port is allocated to the second CDM group, and the DMRS port in the second CDM group is not a predetermined DMRS port.

[0158] Embodiment A5. The WD of any one of embodiments A1-A4, wherein, when at least one spatial layer includes six spatial layers, four DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group, and the two DMRS ports in the second CDM group are super-orthogonal to each other.

[0159] Embodiment A6. The WD of Embodiment A5, wherein two DMRS ports in the second CDM group are not predetermined DMRS ports.

[0160] Embodiment A7. The WD of any one of Embodiments A1-A6, wherein, when at least one spatial layer includes six spatial layers for DMRS type II, two DMRS ports are allocated to a first CDM group, two DMRS ports are allocated to a second CDM group, and two DMRS ports are allocated to a third CDM group, the two DMRS ports in each CDM group are super-orthogonal to each other, and each of the two DMRS ports in the third CDM group is not a predetermined DMRS port.

[0161] Embodiment A8. The WD of any one of Embodiments A1-A6, wherein, when at least one spatial layer includes six spatial layers for DMRS type II, two DMRS ports are allocated to a first CDM group, two DMRS ports are allocated to a second CDM group, and two DMRS ports are allocated to a third CDM group, the two DMRS ports in each CDM group are super-orthogonal to each other, and each of the two DMRS ports in the second CDM group and each of the two DMRS ports in the third CDM group are not predetermined DMRS ports.

[0162] Embodiment A9. The WD of any one of embodiments A1-A6, wherein, when at least one spatial layer includes six spatial layers for DMRS type II, two DMRS ports are allocated to the first CDM group, two DMRS ports are allocated to the second CDM group, and two DMRS ports are allocated to the third CDM group, the two DMRS ports in each CDM group are super-orthogonal to each other, and the two DMRS ports in each CDM group are super-orthogonal to each other and are not predetermined DMRS ports.

[0163] Embodiment A10. The WD of any one of Embodiments A1-A9, wherein, for dual DMRS symbols, the number of CDM groups is minimized by utilizing a frequency domain orthogonal cover code FD-OCC combined with a time domain orthogonal cover code TD-OCC.

[0164] Embodiment B1. A method implemented in a wireless device WD configured to communicate with a network node, the WD configured to allocate a demodulation reference signal (DMRS) port for a physical uplink shared channel (PUSCH) transmission, allocating the DMRS port to at least one of a first code division multiplexing (CDM) group and a second CDM group, wherein the WD is scheduled with more than four PUSCH layers, the method comprising: receiving an indication of a code point of an antenna port field in downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH), the indication indicating at least one spatial layer; and Signaling is transmitted using one or more allocated DMRS ports according to the indication of the code point of the antenna port field.

[0165] Embodiment B2. The method of embodiment B1, wherein, when at least one spatial layer includes five spatial layers, three DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group, and the two DMRS ports in the second CDM group are super-orthogonal to each other.

[0166] Embodiment B3. The method of Embodiment B2, wherein two DMRS ports in the second CDM group are not predetermined DMRS ports.

[0167] Embodiment B4. The method of embodiment B1, wherein, when at least one spatial layer includes five spatial layers, four DMRS ports are allocated to the first CDM group, one DMRS port is allocated to the second CDM group, and the DMRS port in the second CDM group is not a predetermined DMRS port.

[0168] Embodiment B5. The method of any one of embodiments B1-B4, wherein, when at least one spatial layer includes six spatial layers, four DMRS ports are allocated to a first CDM group, and two DMRS ports are allocated to a second CDM group, and the two DMRS ports in the second CDM group are super-orthogonal to each other.

[0169] Embodiment B6. The method of Embodiment B5, wherein two DMRS ports in the second CDM group are not predetermined DMRS ports.

[0170] Embodiment B7. The method of any one of embodiments B1-B6, wherein, when at least one spatial layer includes six spatial layers for DMRS type II, two DMRS ports are allocated to a first CDM group, two DMRS ports are allocated to a second CDM group, and two DMRS ports are allocated to a third CDM group, the two DMRS ports in each CDM group are super-orthogonal to each other, and each of the two DMRS ports in the third CDM group is not a predetermined DMRS port.

[0171] Embodiment B8. The method of any one of embodiments B1-B6, wherein, when at least one spatial layer includes six spatial layers for DMRS type II, two DMRS ports are allocated to a first CDM group, two DMRS ports are allocated to a second CDM group, and two DMRS ports are allocated to a third CDM group, the two DMRS ports in each CDM group are super-orthogonal to each other, and each of the two DMRS ports in the second CDM group and each of the two DMRS ports in the third CDM group are not predetermined DMRS ports.

[0172] Embodiment B9. The method of any one of embodiments B1-B6, wherein, when at least one spatial layer includes six spatial layers for DMRS type II, two DMRS ports are assigned to a first CDM group, two DMRS ports are assigned to a second CDM group, and two DMRS ports are assigned to a third CDM group, the two DMRS ports in each CDM group are super-orthogonal to each other, and the two DMRS ports in each CDM group are super-orthogonal to each other and are not predetermined DMRS ports.

[0173] Embodiment B10. The method of any one of embodiments B1-B9, wherein, for dual DMRS symbols, the number of CDM groups is minimized by utilizing a frequency domain orthogonal cover code FD-OCC combined with a time domain orthogonal cover code TD-OCC.

[0174] Embodiment C1. A network node configured to communicate with a wireless device WD, the WD configured to allocate a demodulation reference signal (DMRS) port for a physical uplink shared channel (PUSCH) transmission, allocating the DMRS port to at least one of a first code division multiplexing (CDM) group and a second CDM group, the WD being scheduled with more than four PUSCH layers and being configured to, and / or including a radio interface and / or processing circuitry and being configured to: Transmitting an indication of a code point of an antenna port field in downlink control information DCI for scheduling a physical uplink shared channel PUSCH, the indication indicating at least one spatial layer; and According to the indication of the code point of the antenna port field, one or more allocated DMRS ports are used to receive signaling.

[0175] Embodiment C2. The network node of embodiment C1, wherein, when the at least one spatial layer includes five spatial layers, three DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group, the two DMRS ports in the second CDM group being super-orthogonal to each other.

[0176] Embodiment C3. The network node of embodiment C2, wherein two DMRS ports in the second CDM group are not predetermined DMRS ports.

[0177] Embodiment C4. The network node of embodiment C1, wherein, when the at least one spatial layer includes five spatial layers, four DMRS ports are allocated to the first CDM group, one DMRS port is allocated to the second CDM group, and the DMRS port in the second CDM group is not a predetermined DMRS port.

[0178] Embodiment C5. The network node of any one of embodiments C1-C4, wherein, when at least one spatial layer includes six spatial layers, four DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group, and the two DMRS ports in the second CDM group are super-orthogonal to each other.

[0179] Embodiment C6. The network node of embodiment C5, wherein two DMRS ports in the second CDM group are not predetermined DMRS ports.

[0180] Embodiment C7. A network node of any one of embodiments C1-C6, wherein, when at least one spatial layer includes six spatial layers for DMRS type II, two DMRS ports are allocated to a first CDM group, two DMRS ports are allocated to a second CDM group, and two DMRS ports are allocated to a third CDM group, the two DMRS ports in each CDM group are super-orthogonal to each other, and each of the two DMRS ports in the third CDM group is not a predetermined DMRS port.

[0181] Embodiment C8. The network node of any one of embodiments C1-C6, wherein, when at least one spatial layer includes six spatial layers for DMRS type II, two DMRS ports are allocated to a first CDM group, two DMRS ports are allocated to a second CDM group, and two DMRS ports are allocated to a third CDM group, the two DMRS ports in each CDM group are super-orthogonal to each other, and each of the two DMRS ports in the second CDM group and each of the two DMRS ports in the third CDM group are not predetermined DMRS ports.

[0182] Embodiment C9. A network node of any one of embodiments C1-C6, wherein, when at least one spatial layer includes six spatial layers for DMRS type II, two DMRS ports are allocated to a first CDM group, two DMRS ports are allocated to a second CDM group, and two DMRS ports are allocated to a third CDM group, the two DMRS ports in each CDM group are super-orthogonal to each other, and the two DMRS ports in each CDM group are super-orthogonal to each other and are not predetermined DMRS ports.

[0183] Embodiment C10. The network node of any of embodiments C1-C9, wherein for dual DMRS symbols, the number of CDM groups is minimized by utilizing a frequency domain orthogonal cover code FD-OCC combined with a time domain orthogonal cover code TD-OCC.

[0184] Embodiment D1. A method implemented in a network node configured to communicate with a wireless device WD, the WD configured to allocate a demodulation reference signal (DMRS) port for a physical uplink shared channel (PUSCH) transmission, the DMRS port being allocated to at least one of a first code division multiplexing (CDM) group and a second CDM group, the WD being scheduled with more than four PUSCH layers, the method comprising: Transmitting an indication of a code point of an antenna port field in downlink control information DCI for scheduling a physical uplink shared channel PUSCH, the indication indicating at least one spatial layer; and According to the indication of the code point of the antenna port field, one or more allocated DMRS ports are used to receive signaling.

[0185] Embodiment D2. The method of embodiment D1, wherein, when at least one spatial layer includes five spatial layers, three DMRS ports are allocated to the first CDM group and two DMRS ports are allocated to the second CDM group, and the two DMRS ports in the second CDM group are super-orthogonal to each other.

[0186] Embodiment D3. The method of Embodiment D2, wherein two DMRS ports in the second CDM group are not predetermined DMRS ports.

[0187] Embodiment D4. The method of embodiment D1, wherein, when at least one spatial layer includes five spatial layers, four DMRS ports are allocated to the first CDM group, one DMRS port is allocated to the second CDM group, and the DMRS port in the second CDM group is not a predetermined DMRS port.

[0188] Embodiment D5. The method of any one of embodiments D1-D4, wherein, when at least one spatial layer includes six spatial layers, four DMRS ports are allocated to a first CDM group, and two DMRS ports are allocated to a second CDM group, and the two DMRS ports in the second CDM group are super-orthogonal to each other.

[0189] Embodiment D6. The method of Embodiment D5, wherein two DMRS ports in the second CDM group are not predetermined DMRS ports.

[0190] Embodiment D7. The method of any one of embodiments D1-D6, wherein, when at least one spatial layer includes six spatial layers for DMRS type II, two DMRS ports are assigned to a first CDM group, two DMRS ports are assigned to a second CDM group, and two DMRS ports are assigned to a third CDM group, the two DMRS ports in each CDM group are super-orthogonal to each other, and each of the two DMRS ports in the third CDM group is not a predetermined DMRS port.

[0191] Embodiment D8. The method of any one of embodiments D1-D6, wherein, when at least one spatial layer includes six spatial layers for DMRS type II, two DMRS ports are allocated to a first CDM group, two DMRS ports are allocated to a second CDM group, and two DMRS ports are allocated to a third CDM group, the two DMRS ports in each CDM group are super-orthogonal to each other, and each of the two DMRS ports in the second CDM group and each of the two DMRS ports in the third CDM group are not predetermined DMRS ports.

[0192] Embodiment D9. The method of any one of embodiments D1-D6, wherein, when at least one spatial layer includes six spatial layers for DMRS type II, two DMRS ports are assigned to a first CDM group, two DMRS ports are assigned to a second CDM group, and two DMRS ports are assigned to a third CDM group, the two DMRS ports in each CDM group are super-orthogonal to each other, and the two DMRS ports in each CDM group are super-orthogonal to each other and are not predetermined DMRS ports.

[0193] Embodiment D10. The method of any one of embodiments D1-D9, wherein for dual DMRS symbols, the number of CDM groups is minimized by utilizing a frequency domain orthogonal cover code FD-OCC combined with a time domain orthogonal cover code TD-OCC.

[0194] Those skilled in the art will appreciate that the concepts described herein can be implemented as methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Thus, the concepts described herein can take the form of all-hardware embodiments, all-software embodiments, or embodiments combining software and hardware, all of which are generally referred to herein as "circuits" or "modules." Any process, step, action, and / or functionality described herein can be performed by, and / or associated with, corresponding modules, which can be implemented in software and / or firmware and / or hardware. In addition, the present disclosure can take the form of a computer program product on a tangible, computer-usable storage medium in which computer program code is implemented, which can be executed by a computer. Any suitable tangible computer-readable medium can be utilized, including a hard disk, CD-ROM, electronic storage device, optical storage device, or magnetic storage device.

[0195] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems, and computer program products. It will be understood that each block in the flowchart illustrations and / or block diagrams, and the combination of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer (thereby creating a special-purpose computer), a special-purpose computer, or other programmable data processing device to produce a machine, so that instructions executed by the processor of the computer or other programmable data processing device create components for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0196] These computer program instructions may also be stored in a computer-readable memory or storage medium, thereby directing a computer or other programmable data processing device to function in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture that includes instruction components that implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0197] Computer program instructions may also be loaded onto a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, such that the instructions executed on the computer or other programmable device provide steps for implementing the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0198] It is understood that the functions / actions noted in the blocks may not occur in the order noted in the operational diagrams. For example, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in the reverse order, depending on the functionality / actions involved. While some figures include arrows on communication paths to illustrate the primary direction of communication, it is understood that communication may occur in the reverse direction of the depicted arrows.

[0199] Computer program code for carrying out operations of the concepts described herein can be used in languages such as Python, The computer program code for performing the operations of the present disclosure may be written in an object-oriented programming language such as C or C++. However, the computer program code for performing the operations of the present disclosure may also be written in a conventional procedural programming language such as the "C" programming language. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer via a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0200] Many different embodiments are disclosed herein in conjunction with the above description and accompanying drawings. It will be understood that literally describing and illustrating every combination and subcombination of these embodiments would be unduly repetitive and obfuscating. Therefore, all embodiments may be combined in any manner and / or combination, and this specification, including the accompanying drawings, should be deemed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, as well as the manner and process of making and using them, and should support claims to any such combination or subcombination.

[0201] Those skilled in the art will appreciate that the embodiments described herein are not limited to what is specifically shown and described herein. In addition, unless otherwise indicated above, it should be noted that all drawings are not drawn to scale. In light of the above teachings, various modifications and variations are possible without departing from the scope of the appended claims.

Claims

1. A wireless device WD (22) configured to communicate with a network node (16), the WD (22) being configured to allocate a demodulation reference signal (DMRS) port for a physical uplink shared channel (PUSCH) transmission, the WD (22) being configured to: receiving an indication of a codepoint of an antenna port field for scheduling a PUSCH, the codepoint indicating allocation of a DMRS port to at least a first code division multiplexing (CDM) group, the indication indicating at least five PUSCH layers; determining a DMRS port configuration based at least in part on the codepoint; and Reference signaling is transmitted according to the determined DMRS port configuration.

2. The WD (22) according to claim 1, wherein The allocation of DMRS ports is configured to maximize the number of mutually super-orthogonal DMRS ports allocated to the first CDM group.

3. The WD (22) according to any one of claims 1 and 2, wherein Two time division orthogonal cover codes TD-OCC are used to allocate all DMRS ports to be allocated to the first CDM group.

4. The WD (22) according to any one of claims 1 and 2, wherein The allocation of DMRS ports is configured to maximize the number of mutually super-orthogonal DMRS ports in the second CDM group.

5. The WD (22) according to any one of claims 1 to 4, wherein When the number of spatial layers is five, three DMRS ports are allocated to the first CDM group, and two DMRS ports are allocated to the second CDM group, the two DMRS ports in the second CDM group being super-orthogonal to each other.

6. The WD (22) according to claims 1-4, wherein When the number of spatial layers is six, four DMRS ports are allocated to the first CDM group, and two DMRS ports are allocated to the second CDM group, the two DMRS ports in the second CDM group being super-orthogonal to each other.

7. The WD (22) according to claims 1-4, wherein When the number of spatial layers is six, two DMRS ports are allocated to the first CDM group, two DMRS ports are allocated to the second CDM group, and two DMRS ports are allocated to the third CDM group, and the two DMRS ports in each CDM group are super-orthogonal to each other.

8. The WD (22) according to any one of claims 1 to 7, wherein For dual DMRS symbols, the number of CDM groups is minimized by utilizing a frequency domain orthogonal cover code FD-OCC combined with a time domain orthogonal cover code TD-OCC.

9. A method in a wireless device WD (22) configured to communicate with a network node (16), the WD (22) being configured to allocate demodulation reference signal (DMRS) ports for physical uplink shared channel (PUSCH) transmission, the method comprising: receiving (S142) an indication of a code point of an antenna port field for scheduling a PUSCH, the code point indicating allocation of a DMRS port to at least a first code division multiplexing (CDM) group, the indication indicating at least five PUSCH layers; determining (S144) a DMRS port configuration based at least in part on the code point; as well as Reference signaling is transmitted (S146) according to the determined DMRS port configuration.

10. The method according to claim 9, wherein: The allocation of DMRS ports is configured to maximize the number of mutually super-orthogonal DMRS ports allocated to the first CDM group.

11. The method according to any one of claims 9 and 10, wherein: Two time division orthogonal cover codes TD-OCC are used to allocate all DMRS ports to be allocated to the first CDM group.

12. The method according to any one of claims 9 and 10, wherein: The allocation of DMRS ports is configured to maximize the number of mutually super-orthogonal DMRS ports in the second CDM group.

13. The method according to claims 9-12, wherein: When the number of spatial layers is five, three DMRS ports are allocated to the first CDM group, and two DMRS ports are allocated to the second CDM group, the two DMRS ports in the second CDM group being super-orthogonal to each other.

14. The method according to claims 9-12, wherein: When the number of spatial layers is six, four DMRS ports are allocated to the first CDM group, and two DMRS ports are allocated to the second CDM group, the two DMRS ports in the second CDM group being super-orthogonal to each other.

15. The method according to claims 9-12, wherein: When the number of spatial layers is six, two DMRS ports are allocated to the first CDM group, two DMRS ports are allocated to the second CDM group, and two DMRS ports are allocated to the third CDM group, and the two DMRS ports in each CDM group are super-orthogonal to each other.

16. The method according to any one of claims 9 to 15, wherein: For dual DMRS symbols, the number of CDM groups is minimized by utilizing a frequency domain orthogonal cover code FD-OCC combined with a time domain orthogonal cover code TD-OCC.

17. A network node (16) configured to communicate with a wireless device WD (22), the WD (22) being configured to allocate a demodulation reference signal (DMRS) port for a physical uplink shared channel (PUSCH) transmission, the network node (16) being configured to: transmitting an indication of a code point of an antenna port field for scheduling a PUSCH, the code point indicating allocation of a DMRS port to at least a first code division multiplexing (CDM) group, the indication indicating at least five PUSCH layers; and Signaling is received using one or more allocated DMRS ports according to the indication of the code point of the antenna port field.

18. The network node (16) according to claim 17, wherein The allocation of DMRS ports is configured to maximize the number of mutually super-orthogonal DMRS ports allocated to the first CDM group.

19. The network node (16) according to any one of claims 17 and 18, wherein Two time division orthogonal cover codes TD-OCC are used to allocate all DMRS ports to be allocated to the first CDM group.

20. The network node (16) according to any one of claims 17 and 18, wherein The allocation of DMRS ports is configured to maximize the number of mutually super-orthogonal DMRS ports in the second CDM group.

21. The network node (16) according to claims 17-20, wherein When the number of spatial layers is five, three DMRS ports are allocated to the first CDM group, and two DMRS ports are allocated to the second CDM group, the two DMRS ports in the second CDM group being super-orthogonal to each other.

22. The network node (16) according to claims 17-20, wherein When the number of spatial layers is six, four DMRS ports are allocated to the first CDM group, and two DMRS ports are allocated to the second CDM group, the two DMRS ports in the second CDM group being super-orthogonal to each other.

23. The network node (16) according to claims 17-20, wherein When the number of spatial layers is six, two DMRS ports are allocated to the first CDM group, two DMRS ports are allocated to the second CDM group, and two DMRS ports are allocated to the third CDM group, and the two DMRS ports in each CDM group are super-orthogonal to each other.

24. The network node (16) according to any one of claims 17-23, wherein For dual DMRS symbols, the number of CDM groups is minimized by utilizing a frequency domain orthogonal cover code FD-OCC combined with a time domain orthogonal cover code TD-OCC.

25. A method in a network node configured to communicate with a wireless device WD (22), the WD (22) being configured to allocate a demodulation reference signal (DMRS) port for a physical uplink shared channel (PUSCH) transmission, the method comprising: transmitting (S148) an indication of a code point of an antenna port field for scheduling a PUSCH, the code point indicating allocation of a DMRS port to at least a first code division multiplexing (CDM) group, the indication indicating at least five PUSCH layers; and According to the indication of the code point of the antenna port field, signaling is received (S150) using one or more allocated DMRS ports.

26. The method according to claim 25, wherein The allocation of DMRS ports is configured to maximize the number of mutually super-orthogonal DMRS ports allocated to the first CDM group.

27. The method according to any one of claims 25 and 26, wherein Two time division orthogonal cover codes TD-OCC are used to allocate all DMRS ports to be allocated to the first CDM group.

28. The method according to any one of claims 25 and 26, wherein The allocation of DMRS ports is configured to maximize the number of mutually super-orthogonal DMRS ports in the second CDM group.

29. The method according to claims 25-28, wherein When the number of spatial layers is five, three DMRS ports are allocated to the first CDM group, and two DMRS ports are allocated to the second CDM group, the two DMRS ports in the second CDM group being super-orthogonal to each other.

30. The method according to claims 25-28, wherein When the number of spatial layers is six, four DMRS ports are allocated to the first CDM group, and two DMRS ports are allocated to the second CDM group, the two DMRS ports in the second CDM group being super-orthogonal to each other.

31. The method according to claims 25-28, wherein: When the number of spatial layers is six, two DMRS ports are allocated to the first CDM group, two DMRS ports are allocated to the second CDM group, and two DMRS ports are allocated to the third CDM group, and the two DMRS ports in each CDM group are super-orthogonal to each other.

32. The method according to any one of claims 25 to 31, wherein: For dual DMRS symbols, the number of CDM groups is minimized by utilizing a frequency domain orthogonal cover code FD-OCC combined with a time domain orthogonal cover code TD-OCC.

Images