Documentation

ltePRS

Positioning reference signal

Syntax

Description

example

sym = ltePRS(enb) returns a column vector containing the positioning reference signal (PRS) symbols for transmission in a single subframe on antenna port 6. These symbols are ordered as they should be mapped into the resource elements along with ltePRSIndices. If, according to the PRS subframe configuration and duplex mode, there is no PRS scheduled in the subframe, then the output vector us empty.

The optional PRSPeriod parameter controls the downlink subframes in which PRS is present. See the ltePRSIndices function reference page for details.

Examples

collapse all

Generate Positioning Reference Signal Symbols

Generate the PRS symbols for subframe 0 of a 10MHz downlink.

Create a cell-wide configuration structure initialized for RMC R.2. Configure for full band PRS (NPRSRB = NDLRB). Configure Iprs = 0, which sets [Tprs Dprs] = [160 0].

rmc = lteRMCDL('R.2');
rmc.NPRSRB = rmc.NDLRB;
rmc.PRSPeriod = 0;
prsSymbols = ltePRS(rmc);

Generate PRS symbols.

prsSymbols(1:4)
ans =

   0.7071 + 0.7071i
   0.7071 + 0.7071i
   0.7071 + 0.7071i
   0.7071 + 0.7071i

Input Arguments

collapse all

enb — Cell-wide settingsstructure

Cell-wide settings, specified as a structure. enb contains the following parameter fields.

The parameters TDDConfig and SSC are only required if DuplexMode is set to 'TDD'.

NDLRB — Number of downlink resource blockspositive scalar integer (6,...,110)

Number of downlink resource blocks, specified as a positive scalar integer from 6 through 110.

Example: 45

Data Types: double

CellRefP — Number of cell-specific reference signal antenna ports1 | 2 | 4

Number of cell-specific reference signal antenna ports, specified as a 1, 2, or 4.

Example: 1

Data Types: double

NCellID — Physical layer cell identity numbernonnegative scalar integer

Physical layer cell identity number, specified as a nonnegative scalar integer.

Example: 4

Data Types: double

NSubframe — Subframe numbernonnegative scalar integer

Subframe number, specified as nonnegative scalar integer.

Example: 5

Data Types: double

NFrame — Frame number0 (default) | optional | nonnegative scalar integer

Frame number, specified as nonnegative scalar integer.

Example: 6

Data Types: double

CyclicPrefix — Cyclic prefix length'Normal' (default) | optional | 'Extended'

Cyclic prefix length, specified as a 'Normal' or 'Extended'.

Data Types: char

DuplexMode — Duplex mode type'FDD' (default) | optional | 'TDD'

Duplex mode type, specified as 'FDD' or 'TDD'. Used for separating the transmission signals.

Data Types: char

TDDConfig — Uplink or downlink configuration for TDD0 (default) | optional | nonnegative scalar integer (0,...,6)

Uplink or downlink configuration for TDD, specified as a nonnegative scalar integer from 0 through 6. Required only for 'TDD' duplex mode.

Example: 4

Data Types: double

SSC — Special subframe configuration0 (default) | optional | nonnegative scalar integer (0,...,9)

Special subframe configuration, specified as nonnegative scalar integer from 0 through 9. Required only for 'TDD' duplex mode.

Example: 6

Data Types: double

NPRSRB — Number of PRS physical resource blocks0,...,NDLRB

Number of PRS physical resource blocks, specified as nonnegative scalar integer from 0 through NDLRB.

Example: 8

Data Types: double

PRSPeriod — Positioning reference signal (PRS) period'On' (default) | optional | 'Off' | [Iprs] | [Tprs Dprs]

Positioning reference signal (PRS) period, specified as 'On', 'Off', a numeric scalar, or a 1-by-2 vector. This parameter controls the downlink subframes in which PRS will be present. For details, see ltePRSIndices.

Example: 0

Example: [160 0]

Data Types: char | double

Output Arguments

collapse all

sym — Positioning Reference Signal (PRS) symbolscomplex numeric column vector

Positioning Reference Signal (PRS) symbols, returned as complex numeric column vector, for transmission in a single subframe on antenna port 6.

Example: 0.7071 + 0.7071i

Data Types: double
Complex Number Support: Yes

Introduced in R2014a

Was this topic helpful?