Documentation

ltePUCCH3DRSIndices

PUCCH format 3 DRS resource element indices

Syntax

  • [ind,info] = ltePUCCH3DRSIndices(ue,chs)
    example
  • [ind,info] = ltePUCCH3DRSIndices(ue,chs,opts)

Description

example

[ind,info] = ltePUCCH3DRSIndices(ue,chs) returns a matrix of resource element indices, ind, given the UE-specific settings structure, ue, and channel transmission configuration, chs. It returns a matrix of resource element indices, ind, and information structure array, info, for the Demodulation Reference Signal (DRS) associated with PUCCH Format 3 transmission. By default, the indices are returned in 1-based linear indexing form that can directly index elements of a resource matrix. These indices are ordered as the PUCCH format 3 DRS modulation symbols should be mapped. Alternative indexing formats can also be generated. The indices for each antenna are in the columns of ind, with the number of columns determined by the number of PUCCH resource indices specified.

[ind,info] = ltePUCCH3DRSIndices(ue,chs,opts) allows control of the format of the returned indices through a cell array, opts, of option strings.

Examples

collapse all

Generate PUCCH Format 3 DRS Indices

Generate indices for the demodulation reference signal (DRS) associated with a PUCCH format 3 transmission of 1.4 MHz bandwidth, using PUCCH Resource Index 0.

ind = ltePUCCH3DRSIndices(struct('NULRB',6),struct('ResourceIdx',0));
ind(1:4)
          73
          74
          75
          76

Input Arguments

collapse all

ue — UE-specific settingsstructure

UE-specific settings, specified as a structure. ue can contain the following fields.

NULRB — Number of uplink resource blocksscalar integer

Number of uplink resource blocks, specified as a scalar integer.

Data Types: double

CyclicPrefixUL — Cyclic prefix length'Normal' (default) | Optional | 'Extended'

Cyclic prefix length for uplink, specified as either 'Normal' or 'Extended'. Optional.

Data Types: char

Data Types: struct

chs — Channel transmission configurationstructure

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

ResourceIdx — PUCCH Resource Indicescolumn vector of integers with values ranging from 0 to 549

PUCCH Resource Indices, specified as a column vector of integers with values from 0...549. There is one index for each transmission antenna. The indices determine the physical resource blocks used for transmission. (n3_pucch). This input argument is optional.

Data Types: double

Data Types: struct

opts — Format control for returned element resource indices'ind', '1based' (default) | 'sub' | '0based'

Format control for returned element resource indices, specified as a string or a cell array of strings. The option strings can contain values from the Indexing Style and Index base categories.

Category

Options

Description

Indexing style

'ind' (default)

The returned indices are in linear index form.

'sub'

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

Index base

'1based' (default)

Indices returned are 1-based.

'0based'

Indices returned are 0-based.

Data Types: char | cell

Output Arguments

collapse all

ind — Resource element indicesmatrix of integer values

Resource element indices, returned as a matrix of integer values. The indices for each antenna form the columns of ind, with the number of columns determined by the number of PUCCH Resource Indices specified.

Data Types: uint32

info — Information associated with PUCCH format 3 transmissionscalar structure | structure array

Information associated with PUCCH format 3 transmission, returned as a scalar structure or a structure array. It contains the following fields.

PRBSet — PRBs occupied by indicesrow vector of integers

PRBs occupied by the indices in each slot of the subframe (0-based), specified as a row vector of integers.

Data Types: double

RBIdx — PUCCH logical resource block indexscalar integer

PUCCH logical resource block index (m), specified as a scalar integer.

Data Types: double

Data Types: struct

Introduced in R2014a

Was this topic helpful?