Main Content

ltePUSCHDRSIndices

PUSCH DM-RS resource element indices

collapse all in page

Syntax

ind = ltePUSCHDRSIndices(ue,chs)
ind = ltePUSCHDRSIndices(ue,chs,opts)

Description

ind = ltePUSCHDRSIndices(ue,chs) returns a matrix of resource element (RE) indices for the demodulation reference signal (DM-RS) associated with the physical uplink shared channel (PUSCH) transmission, given structures containing the UE-specific settings and the channel transmission configuration settings.

If indices for a number of layers, NU, are required, rather than indices for NTxAnts, the first NU columns of the output can be used. The first NU columns of ind are the appropriate indices for the layerseq output from the ltePUSCHDRS function.

example

ind = ltePUSCHDRSIndices(ue,chs,opts) formats the returned indices using options specified by opts.

example

Examples

collapse all

Open Live Script

Generate PUSCH DM-RS resource element indices for the uplink reference measurement channel A3-1.

ue = lteRMCUL('A3-1');
puschInd = ltePUSCHDRSIndices(ue,ue.PUSCH);
puschInd(1:4)
ans = 4x1 uint32 column vector

   217
   218
   219
   220
Open Live Script

Generate the zero-based PUSCH DM-RS indices for the uplink reference measurement channel A3-3.

ue = lteRMCUL('A3-3');
puschInd = ltePUSCHDRSIndices(ue,ue.PUSCH,{'0based','ind'});
puschInd(1:4)
ans = 4x1 uint32 column vector

   540
   541
   542
   543

Input Arguments

collapse all

UE-specific settings, specified as a structure having the following fields.

Number of uplink resource blocks, specified as an integer.

Data Types: double

Cyclic prefix length for uplink (UL), specified as either 'Normal' or 'Extended'.

Data Types: char | string

Number of transmission antennas, specified as 1, 2, or 4.

Data Types: double

Data Types: struct

Channel transmission configuration, specified as a structure having the following fields.

Physical resource block (PRB) indices, specified as a column integer vector or two-column integer matrix. The PRB indices correspond to the slot-wise resource allocations for this PUSCH.

  • When specified as a column vector, the resource allocation is the same in both slots of the subframe.

  • When specified as a two-column matrix, the resource allocations can vary for each slot in the subframe.

The PRB indices are zero-based.

Data Types: double

Data Types: struct

Output format options for resource element indices, specified as a character vector, cell array of character vectors, or string array. For convenience, you can specify several options as a single character vector or string scalar by a space-separated list of values placed inside the quotes. Values for opts when specified as a character vector include (use double quotes for string) :

Category Options Description

Indexing style

'ind' (default)

The returned indices are in linear index style.

'sub'

The returned indices are in [subcarrier,symbol,port] subscript row style.

Index base

'1based' (default)

The returned indices are one-based.

'0based'

The returned indices are zero-based.

Example: 'ind 1based', "ind 1based", {'ind','1based'}, or ["ind","1based"] specify the same formatting options.

Data Types: char | string | cell

Output Arguments

collapse all

PUSCH DM-RS resource element indices, returned as an NSC-by-NTX integer matrix. NSC is the number of DM-RS indices per antenna, and NTX is the number of transmission antennas. The resource element (RE) indices for the demodulation reference signal (DM-RS) are associated with PUSCH transmission. By default, the indices are returned in one-based linear indexing form that can directly index elements of a resource matrix. These indices are ordered according to the PUSCH DM-RS modulation symbol mapping specified in TS 36.211 [1], Section 5.5.2. The opts input offers alternative indexing formats.

Data Types: uint32

References

[1] 3GPP TS 36.211. “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation.” 3rd Generation Partnership Project; Technical Specification Group Radio Access Network. URL: https://www.3gpp.org.

Version History

Introduced in R2014a

See Also

| | | | |