Documentation

This is machine translation

Translated by Microsoft
Mouseover text to see original. Click the button below to return to the English verison of the page.

Note: This page has been translated by MathWorks. Please click here
To view all translated materals including this page, select Japan from the country navigator on the bottom of this page.

lteRMCDLTool

Downlink RMC waveform generation

Syntax

  • [waveform,grid,rmccfgout] = lteRMCDLTool
    example
  • [waveform,grid,rmccfgout] = lteRMCDLTool(rmccfg,trdata)
    example
  • [waveform,grid,rmccfgout] = lteRMCDLTool(rc,trdata,duplexmode,totsubframes)
    example

Description

example

[waveform,grid,rmccfgout] = lteRMCDLTool starts a user interface for the parameterization and generation of the reference measurement channel (RMC) waveform, the resource element grid, and an RMC configuration structure. The main function outputs are specified in the user interface but can also be assigned to variables. See DL Reference Channel Options for a list of the default top-level configuration associated with the available downlink reference channels.

example

[waveform,grid,rmccfgout] = lteRMCDLTool(rmccfg,trdata) where rmccfg specifies a user-defined reference channel structure. The reference configuration structure with default parameters can easily be created using lteRMCDL then modified if desired.

    Note:   SIB1 messages and the associated PDSCH and PDCCH can be added to the output waveform by adding the substructure rmccfg.SIB.

example

[waveform,grid,rmccfgout] = lteRMCDLTool(rc,trdata,duplexmode,totsubframes) specifies the default reference measurement channel, rc, and information bits trdata. duplexmode and totsubframes are optional input arguments, that define the duplex mode of the generated waveform and total number of subframes that make up the grid.

Examples

collapse all

Open the LTE user interface to generate a downlink reference measurement channel waveform.

The LTE Downlink RMC Generator dialog box appears when you execute the lteRMCDLTool function with no input arguments.

lteRMCDLTool

You can use the user interface to generate the default waveform or adjust default settings prior to waveform generation.

Generate a time domain signal and a 3-dimensional array of the resource elements for R.31-4 FDD as specified in TS 36.101 Annex A.3.9.1-1. R.31-4 FDD is 20MHz, 64QAM, variable code rate and has user data scheduled in subframe 5.

[txWaveform,txGrid,rmcCfgOut] = lteRMCDLTool('R.31-4',{[1;0] [1;0]});

This example shows use of lteRMCDLTool to generate a tx waveform with SIB transmission enabled using DCIFormat1A and localized allocation.

Specify desired RMC, initialize configuration structure and define txData. Generate txGrid and plot it.

rc = 'R.3';
rmc = lteRMCDL(rc);

txData = [1;0;0;1];
[~,txGrid,~] = lteRMCDLTool(rmc, txData);
mesh(abs(txGrid))
view(2)

To insert SIB1 message into the output waveform, initialize SIB substructure, enable SIB transmission, adjust other defaults, and regenerate txGrid. Plot txGrid to illustrate the presence of SIB1 message in subframe 5

rmc.SIB.Enable = 'On';
rmc.SIB.DCIFormat = 'Format1A';
rmc.SIB.AllocationType = 0;
rmc.SIB.VRBStart = 8;
rmc.SIB.VRBLength = 8;
rmc.SIB.Data = randi([0 1],144,1);

[txWaveform,txGrid,rmcCfgOut] = lteRMCDLTool(rmc, txData);
figure
mesh(abs(txGrid))
view(2)

Generate a time domain waveform, and a 3D array of the resource elements for RMC R.12 as specified in TS 36.101. Modify the standard R.12 RMC to use 16QAM modulation scheme instead of the default QPSK.

Create an RMC setting structure specifying R.12 for RC and 16QAM for Modulation.

rmc.RC = 'R.12';
rmc.PDSCH.Modulation = '16QAM';

Generate the tx waveform, RE grid and also output the RMC configuration structure.

txData = [1;0;0;1];
[txWaveform, txGrid, rmcCfgOut] = lteRMCDLTool(rmc, txData);

Review the rmcCgfOut structure and PDSCH substructure.

rmcCfgOut
rmcCfgOut.PDSCH
rmcCfgOut = 

  struct with fields:

                 RC: 'R.12'
              NDLRB: 6
           CellRefP: 4
            NCellID: 0
       CyclicPrefix: 'Normal'
                CFI: 3
        PCFICHPower: 0
                 Ng: 'Sixth'
      PHICHDuration: 'Normal'
              HISet: [112×3 double]
         PHICHPower: 0
             NFrame: 0
          NSubframe: 0
       TotSubframes: 10
          Windowing: 0
         DuplexMode: 'FDD'
              PDSCH: [1×1 struct]
    OCNGPDCCHEnable: 'Off'
     OCNGPDCCHPower: 0
    OCNGPDSCHEnable: 'Off'
     OCNGPDSCHPower: 0
          OCNGPDSCH: [1×1 struct]
          SerialCat: 1
       SamplingRate: 1920000
               Nfft: 128


ans = 

  struct with fields:

               TxScheme: 'TxDiversity'
             Modulation: {'16QAM'}
                NLayers: 4
                    Rho: 0
                   RNTI: 1
                  RVSeq: [0 1 2 3]
                     RV: 0
         NHARQProcesses: 8
           NTurboDecIts: 5
                 PRBSet: [6×1 double]
         TargetCodeRate: 0.3333
         ActualCodeRate: [1×10 double]
             TrBlkSizes: [0 936 936 936 936 0 936 936 936 936]
        CodedTrBlkSizes: [0 2496 2496 2496 2496 0 2496 2496 2496 2496]
              DCIFormat: 'Format1'
            PDCCHFormat: 2
             PDCCHPower: 0
                CSIMode: 'PUCCH 1-1'
                PMIMode: 'Wideband'
    HARQProcessSequence: [1×70 double]

Display the PRB allocations associated with the sequence of subframes in a frame for DCI Format 0 and uplink resource allocation type 1.

Configure a type 1 uplink resource allocation (multi-cluster). TS 36.213, Section 8.1.2 describes the resourse indication value (RIV) determination.

enb = struct('NDLRB',50);
dci = lteDCI(enb,struct('DCIFormat','Format0','AllocationType',1));
dci.Allocation.RIV = 1;

Display an image of the PRBs used in each slot of each subframe in a frame.

  • Create a subframeslots matrix full of zeros. There are 20 slots per frame, specifically two slots per subframe and ten subframes per frame.

  • Loop through assigning a PRB set of indices for each subframe. Also assign a value in subframeslots for each occupied PRB index.

subframeslots = zeros(enb.NDLRB,20);
for i = 0:9
    enb.NSubframe = i;
    prbSet = lteDCIResourceAllocation(enb,dci);
    prbSet = repmat(prbSet,1,2/size(prbSet,2));
    for s = 1:2
        subframeslots(prbSet(:,s)+1,2*i+s) = 20+s*20;
    end
end
image(subframeslots);
axis xy;
xlabel('Subframe Slots');
ylabel('PRB Indices');

Observe from the image that the same set of PRB indices is used in each slot.

Display the PRB allocations associated with the sequence of subframes in a frame for an uplink resource allocation with hopping.

Configure a type 1 uplink resource allocation that has type 0 hopping and slot and subframe hopping.

enb = struct('NDLRB',50,'NCellID',0);
dci = lteDCI(enb,struct('DCIFormat','Format0','AllocationType',0,...
    'FreqHopping',1));
dci.Allocation.HoppingBits = 0;
dci.Allocation.RIV = 110;
enb.PUSCHHopping = 'InterAndIntra';
enb.MacTxNumber = 0;
enb.NSubbands = 1;
enb.PUSCHHoppingOffset = 10;

Display an image of the PRBs used in each slot of each subframe in a frame.

  • Create a subframeslots matrix full of zeros. There are 20 slots per frame, specifically two slots per subframe and ten subframes per frame.

  • Loop through assigning a PRB set of indices for each subframe. Also assign a value in subframeslots for each occupied PRB index.

subframeslots = zeros(enb.NDLRB,20);
for i = 0:9
    enb.NSubframe = i;
    prbSet = lteDCIResourceAllocation(enb,dci);
    prbSet = repmat(prbSet,1,2/size(prbSet,2));
    for s = 1:2
        subframeslots(prbSet(:,s)+1,2*i+s) = 20+s*20;
    end
end
image(subframeslots)
axis xy
xlabel('Subframe Slots')
ylabel('PRB Indices')

Observe from the image that the occupied PRB indices hops in odd and even slots.

Related Examples

Input Arguments

collapse all

Reference channel, specified as a character vector. This argument identifies the reference measurement channel (RMC) number, as specified in TS 36.101, [1]. See DL Reference Channel Options for a list of the default top-level configuration associated with the available downlink reference channels.

Data Types: char

Information bits, specified as a vector or cell array containing one or two vectors of bit values. Each vector contains the information bits stream to be coded across the duration of the generation, which represents multiple concatenated transport blocks. If the number of bits required across all subframes of the generation exceeds the length of the vectors provided, the txdata vector is looped internally. This feature allows you to enter a short pattern, such as [1;0;0;1], which is repeated as the input to the transport coding. In each subframe of generation, the number of data bits taken from this stream comes from the elements of the rmccfgout.PDSCH.TrBlkSizes matrix.

When the trdata input contains empty vectors, there is no transport data. The transmission of PDSCH and its corresponding PDCCH are skipped in the waveform when the trdata contains empty vectors. The other physical channels and signals are transmitted as normal in generated waveform.

Example: [1;0;0;1]

Data Types: double | cell
Complex Number Support: Yes

Duplexing mode, specified as 'FDD' or 'TDD' to indicate the frame structure type of the generated waveform.

Data Types: char

Total number of subframes, specified as a numeric scalar. Optional. This argument specifies the total number of subframes that form the resource grid.

Data Types: double

Reference channel configuration, specified as a structure. The structure defines any (or all) of the fields or subfields. The reference configuration structure with default parameters can easily be created using the lteRMCDL function. lteRMCDL generates the various RMC configuration structures, as defined in TS 36.101 [1], Annex A.3.

You can use the lteRMCDL output configuration structure without change or modify it to align with your simulation requirements to generate the output waveform. SIB1 messages and the associated PDSCH and PDCCH can be added to the output waveform by adding the substructure rmccfg.SIB. rmccfg may include fields contained in the output structure, rmccfgout.

Data Types: struct

Output Arguments

collapse all

Generated RMC time-domain waveform, returned as a NS-by-NTX numeric matrix. NS is the number of time-domain samples and NTX is the number of antennas.

Data Types: double
Complex Number Support: Yes

Populated resource grid, returned as a numeric 3-D array of resource elements for several subframes across all configured antenna ports, as described in Data Structures.

grid represents the populated resource grid for all the physical channels specified in TS 36.101 [1], Annex A.3.

Data Types: double
Complex Number Support: Yes

RMC configuration output structure

RMC configuration, returned as a scalar structure. rmccfgout contains information about the OFDM-modulated waveform and RMC-specific configuration parameters. Field definitions and settings align with rmccfg.

For more information about the OFDM modulated waveform, see lteOFDMInfo. For more information about the RMC-specific configuration parameters, see lteRMCDL.

Parameter FieldValuesDescription
RC

'R.0' (default), 'R.1', 'R.2', 'R.3', 'R.4', 'R.5', 'R.6', 'R.7', 'R.8', 'R.9', 'R.10', 'R.11', 'R.12', 'R.13', 'R.14', 'R.25', 'R.26', 'R.27', 'R.28', 'R.31-3A', 'R.31-4', 'R.43', 'R.44', 'R.45', 'R.45-1', 'R.48', 'R.50', 'R.51', 'R.6-27RB', 'R.12-9RB', 'R.11-45RB'

Reference measurement channel (RMC) number or type, as specified in TS 36.101, Annex A.3.

  • 'R.31-3A' and 'R.31-4' are sustained data rate RMCs with user data in subframe 5.

  • 'R.6-27RB', 'R.12-9RB', and 'R.11-45RB' are custom RMCs configured for non-standard bandwidths that maintain the same code rate as the standardized versions defined in TS 36.101, Annex A.3.

NDLRB

Scalar integer from 6 to 110

Number of downlink resource blocks. (NRBDL)

CellRefP

1, 2, 4

Number of cell-specific reference signal (CRS) antenna ports

NCellD

Integer from 0 to 503

Physical layer cell identity

CyclicPrefix

'Normal' (default), 'Extended'

Cyclic prefix length

CFI

1, 2, or 3
Scalar or if the CFI varies per subframe, a vector of length 10 (corresponding to a frame).

Control format indicator (CFI) value. In TDD mode, CFI varies per subframe for the RMCs ('R.0', 'R.5', 'R.6', 'R.6-27RB', 'R.12-9RB')

See footnote 1.
PCFICHPower

0 (default), numeric scalar

PCFICH symbol power adjustment, in dB

Ng

'Sixth', 'Half', 'One', 'Two'

HICH group multiplier

PHICHDuration

'Normal', 'Extended'

PHICH duration

HISet

Matrix with default size 112-by-3.

Contains the maximum PHICH groups (112) as per TS 36.211, Section 6.9 with the first PHICH sequence of each group set to ACK). For further details, see ltePHICH.

PHICHPower

0 (default), numeric scalar

PHICH symbol power in dB.

NFrame

0 (default), nonnegative scalar integer

Frame number

NSubFrame

0 (default), nonnegative scalar integer

Subframe number

TotSubFrames

Nonnegative scalar integer

Total number of subframes to generate

Windowing

Nonnegative scalar integer

Number of time-domain samples over which windowing and overlapping of OFDM symbols is applied

DuplexMode

'FDD' (default), 'TDD'

Duplexing mode, specified as:

  • 'FDD' for Frequency Division Duplex or

  • 'TDD' for Time Division Duplex

This field is only present and applicable for 'Port7-14' transmission scheme (TxScheme)
  CSIRSPeriod

'On' (default), 'Off', Icsi-rs (0,...,154), [Tcsi-rs Dcsi-rs]. You can also specify values in a cell array of configurations for each resource.

CSI-RS subframe configurations for one or more CSI-RS resources. Multiple CSI-RS resources can be configured from a single common subframe configuration or from a cell array of configurations for each resource.

The following fields are only present and applicable for 'Port7-14' transmission scheme (TxScheme) and only required in rmccfg if CSIRSPeriod is not set to 'Off'.

  CSIRSConfig

Scalar integer

Array CSI-RS configuration indices. See TS 36.211, Table 6.10.5.2-1.

  CSIRefP

1 (default), 2, 4, 8

Array of number of CSI-RS antenna ports

These fields are only present and applicable for 'Port7-14' transmission scheme (TxScheme)
  ZeroPowerCSIRSPeriod

'Off' (default), 'On', Icsi-rs (0,...,154), [Tcsi-rs Dcsi-rs]. You can also specify values in a cell array of configurations for each resource.

Zero power CSI-RS subframe configurations for one or more zero power CSI-RS resource configuration index lists. Multiple zero power CSI-RS resource lists can be configured from a single common subframe configuration or from a cell array of configurations for each resource list.

The following field is only applicable for 'Port7-14' transmission scheme (TxScheme) and only required in rmccfg if CSIRSPeriod is not set to 'Off'.

  ZeroPowerCSIRSConfig

16-bit bitmap character vector (truncated if not 16 bits or '0' MSB extended), or a numeric list of CSI-RS configuration indices. You can also specify values in a cell array of configurations for each resource.

Zero power CSI-RS resource configuration index lists (TS 36.211 Section 6.10.5.2). Specify each list as a 16-bit bitmap character vector (if less than 16 bits, then '0' MSB extended). or as a numeric list of CSI-RS configuration indices from TS 36.211 Table 6.10.5.2-1 in the '4' CSI reference signal column. Multiple lists can be defined using a cell array of bitmap character vectors or numerical lists.

PDSCH

Scalar structure

PDSCH transmission configuration substructure

SIB

Scalar structure

Include a SIB message by adding the SIB substructure to the lteRMCDL function configuration output structure, rmccfgout, after it is generated and before using the rmccfgout structure as input to lteRMCDLTool.

OCNGPDCCHEnable

'Off', 'On'

Enable PDCCH OFDMA channel noise generator (OCNG).

See footnote 2.
OCNGPDCCHPower

Scalar integer, 0 (default)

PDCCH OCNG power in dB

OCNGPDSCHEnable

'Off', 'On'

Enable PDSCH OCNG

OCNGPDSCHPower

Scalar integer, defaults to PDSCH.Rho (default)

PDSCH OCNG power in dB

OCNGPDSCH

Scalar structure

PDSCH OCNG configuration substructure

OCNG

'Off', 'On'. ‘Disable' and 'Enable' are also accepted.

OFDMA channel noise generator

    Note:   This parameter will be removed in a future release. Use the PDCCH and PDSCH-specific OCNG parameters instead.

The following fields are only present and applicable for 'TDD' duplex mode (DuplexMode).

  SSC

0 (default), 1, 2, 3, 4, 5, 6, 7, 8, 9

Special subframe configuration (SSC)

  TDDConfig

0 (default), 1, 2, 3, 4, 5, 6

Uplink–downlink configuration

SamplingRate

Numeric scalar

Carrier sampling rate in Hz, (NSC/NSYM) × 3.84e6, where NSC is the number of subcarriers and NSYM is the number of OFDM symbols in a subframe.

Nfft

Scalar integer, typically one of {128, 256, 512, 1024, 1536, 2048} for standard channel bandwidths {'1.4MHz', '3MHz', '5MHz', '10MHz', '15MHz', '20MHz'}, respectively.

Number of FFT frequency bins

  1. CFI is equal to the number of symbols allocated to:

    • PDCCH - 1 for NDLRB < 10

    • PDCCH for NDLRB >= 10

    For the RMCs, the number of symbols allocated to PDCCH varies with channel bandwidth setting,

    • 2 symbols for 20 MHz, 15 MHz, and 10 MHz

    • 3 symbols for 5 MHz and 3 MHz

    • 4 symbols for 1.4 MHz

    In the TDD mode, only two OFDM symbols are allocated to PDCCH in subframes 1 and 6 irrespective of the channel bandwidth. Therefore, the CFI value varies per subframe for the 5 MHz and 3 MHz and 1.4 MHz channel bandwidths, that is for bandwidths where PDCCH symbol allocation is not two for other subframes.

  2. The PDCCH ONCG fills the unused PDCCH resource elements with QPSK symbols using either single port or transmit diversity depending on the number of cell RS ports.

PDSCH substructure

The substructure PDSCH relates to the physical channel configuration and contains these fields:

Parameter FieldValuesDescription
TxScheme

'Port0', 'TxDiversity', 'CDD', 'SpatialMux', 'MultiUser', 'Port5', 'Port7-8', 'Port8', 'Port7-14'.

PDSCH transmission scheme, specified as one of the following options.

Transmission schemeDescription
'Port0'Single antenna port, port 0
'TxDiversity'Transmit diversity
'CDD'Large delay cyclic delay diversity scheme
'SpatialMux'Closed loop spatial multiplexing
'MultiUser'Multi-user MIMO
'Port5'Single-antenna port, port 5
'Port7-8'Single-antenna port, port 7, when NLayers = 1. Dual layer transmission, ports 7 and 8, when NLayers = 2.
'Port8'Single-antenna port, port 8
'Port7-14'Up to eight layer transmission, ports 7–14

Modulation

'QPSK', '16QAM', '64QAM', or '256QAM'

Modulation type, specified as a character vector or cell array of character vectors. If blocks, each cell is associated with a transport block.

NLayers

Integer from 1 to 8

Number of transmission layers.

Rho

0 (default), Numeric scalar

PDSCH resource element power allocation, in dB

RNTI

0 (default), scalar integer

Radio network temporary identifier (RNTI) value (16 bits)

RVSeq

Integer vector (0,1,2,3), specified as a one or two row matrix (for one or two codewords)

Specifies the sequence of Redundancy Version (RV) indicators for each HARQ process. The number of elements in each row is equal to the number of transmissions in each HARQ process. If RVSeq is a row vector in a two codeword transmission, then the same RV sequence is applied to both codewords.

RV

Integer vector (0,1,2,3). A one or two column matrix (for one or two codewords).

Specifies the redundancy version for one or two codewords used in the initial subframe number, NSubframe. This parameter field is only for informational purposes and is Read-Only.

NHARQProcesses

1, 2, 3, 4, 5, 6, 7, or 8

Number of HARQ processes

NTurboDecits

5 (default), nonnegative scalar integer

Number of turbo decoder iteration cycles

PRBSet

Integer column vector or two-column matrix

Zero-based physical resource block (PRB) indices corresponding to the slot wise resource allocations for this PDSCH. PRBSet can be assigned as:

  • a column vector, the resource allocation is the same in both slots of the subframe,

  • a two-column matrix, this parameter specifies different PRBs for each slot in a subframe,

  • a cell array of length 10 (corresponding to a frame, if the allocated physical resource blocks vary across subframes).

PRBSet varies per subframe for the RMCs 'R.25'(TDD), 'R.26'(TDD), 'R.27'(TDD), 'R.43'(FDD), 'R.44', 'R.45', 'R.48', 'R.50', and 'R.51'.

TargetCodeRate

Numeric scalar or one or two row numeric matrix

Target code rates for one or two codewords for each subframe in a frame. Used for calculating the transport block sizes according to TS 36.101 [1], Annex A.3.1.

If both TargetCodeRate and TrBlkSizes are not provided at the input, and the RC does not have a single ratio target code rate in TS 36.101, Table A.3.1.1-1, TargetCodeRate == ActualCodeRate.

ActualCodeRate

One or two row numeric matrix

Actual code ratesfor one or two codewords for each subframe in a frame, calculated according to TS 36.101 [1], Annex A.3.1. The maximum actual code rate is 0.93. This parameter field is only for informational purposes and is read-only.

TrBlkSizes

One or two row numeric matrix

Transport block sizes for each subframe in a frame

CodedTrBlkSizes

One or two row numeric matrix

Coded transport block sizes for one or two codewords. This parameter field is only for informational purposes.

DCIFormat

'Format0', 'Format1', 'Format1A', 'Format1B', 'Format1C', 'Format1D', 'Format2', 'Format2A', 'Format2B', 'Format2C', 'Format2D', 'Format3', 'Format3A', 'Format4', 'Format5'

Downlink control information (DCI) format type of the PDCCH associated with the PDSCH. See lteDCI.

PDCCHFormat

0, 1, 2, 3

Aggregation level of PDCCH associated with PDSCH

PDCCHPowerNumeric scalar

PDCCH power in dB

CSIMode

'PUCCH 1-0', 'PUCCH 1-1', 'PUSCH 1-2', 'PUSCH 3-0', 'PUSCH 3-1'

CSI reporting mode

PMIMode

'Wideband' (default), 'Subband'

PMI reporting mode. PMIMode='Wideband' corresponds to PUSCH reporting Mode 1-2 or PUCCH reporting Mode 1-1 (PUCCH Report Type 2) and PMIMode='Subband' corresponds to PUSCH reporting Mode 3-1.

The following field is only present for 'SpatialMux' transmission scheme (TxScheme).
  PMISet

Integer vector with element values from 0 to 15.

Precoder matrix indication (PMI) set. It can contain either a single value, corresponding to single PMI mode, or multiple values, corresponding to multiple or subband PMI mode. The number of values depends on CellRefP, transmission layers and TxScheme. For more information about setting PMI parameters, see ltePMIInfo.

The following field is only present for 'Port7-8', 'Port8', or 'Port7-14' transmission schemes (TxScheme).
  NSCID

0 (default), 1

Scrambling identity (ID)

The following fields are only present for UE-specific beamforming ('Port5', 'Port7-8', 'Port8', or 'Port7-14').
  WNumeric matrix

NLayers-by-P precoding matrix for the wideband UE-specific beamforming of the PDSCH symbols. P is the number of transmit antennas. An empty matrix, [], signifies no precoding.

  NTxAnts

Nonnegative scalar integer

Number of transmission antennas.

HARQProcessSequence

1-by-LHARQ_Seq integer vector.

One-based HARQ process indices for the internal HARQ scheduling sequence, optimized for 8 HARQ processes in FDD mode and for 7 HARQ processes in TDD mode (corresponding to UL/DL configuration 1).

See footnote 2.

  1. The function returns valid TrBlkSizes and CodedTrBlkSizes set to 0 when PRBSet is empty, indicating there is no PDSCH allocation in this frame.

  2. When creating the HARQProcessSequence, the length (LHARQ_Seq) is determined based on these conditions:

    1. For FDD —

      1. When configuration uses NHARQProcesses = 8,

        1. If subframe 5 is active, use HARQProcessSequence length 30. The transmission subframes 1,2,3,4,6,7,8,9 have the same transport block size and subframes 0 and 5 have different transport block sizes from other subframes and each other.

        2. If subframe 5 is not active, use HARQProcessSequence length 70. The transmission subframes 1,2,3,4,6,7,8,9 have the same transport block size and subframes 0 and 5 the same transport block size but different transport block sizes than other subframes.

      2. When configuration uses NHARQProcesses = 1,

        1. Use HARQProcessSequence length 10 (one frame). Only the TrBlkSize corresponding to subframe 0 gets transmitted, no transmission in other subframes even if the transport block sizes in other subframes are non-zero.

    2. For TDD —

      1. If subframe 5 is active, use HARQProcessSequence length 20.

      2. If subframe 5 is not active, use HARQProcessSequence length 60.

      3. When configuration uses TDDConfig = 1:

        1. Use NHARQProcesses = 7.

        2. All downlink and special subframes have nonzero transport block size. The transport block size of subframe 0 is different than subframe {1,6} and different than subframe {4,9}.

SIB substructure

If the substructure SIB has been added to rmccfg, SIB1 messages and the associated PDSCH and PDCCH can be generated. The SIB substructure includes these fields:

Parameter FieldValuesDescription
Data

(0,1), bit array

SIB1 transport block information bits

See footnote 1.

VRBStart

variable, see rules in TS 36.213 Section 7.1.6.3

Virtual RB allocation starting resource block, RBstart.

VRBLength

variable, see rules in TS 36.213 Section 7.1.6.3

Length in terms of virtualy contiguously allocated resource blocks, LCRBs.

Enable

'On' (default), 'Off'

Enable/Disable SIB generation

DCIFormat

'Format1A' (default) or 'Format1C'

Downlink control information (DCI) format

AllocationType

0 (default) or 1, single bit flag

Localized (0) or distributed (1) allocation of virtual resource blocks for Resource allocation type 2

The following parameter is only applicable when DCIFormat = 'Format1A'.

N1APRB

2 or 3

Transport block set selection parameter, NPRB1A

Indicates the column in TS 36.213, Table 7.1.7.2.1-1 for transport block size selection. The default is the smallest transport block size, in either column 2 or 3, that provides a valid transport block size bigger than or equal to the length of the Data field. Also see TS 36.212 Section 5.3.3.1.3 and TS 36.213 Section 7.1.7.

The following parameter is only applicable when using distributed allocation (AllocationType = 1).

Gap

0 or 1

Distributed allocation gap, ‘0' for Ngap,1 or ‘1' for Ngap,2

  1. The set of valid transport block sizes is specified in TS 36.213 [4], Table 7.1.7.2.1-1. Only columns 2 and 3 apply to the SIB DL-SCH. The Data field is padded with zeros to the closest valid size from this table.

    Note:  

    • Per TS 36.321 [5], Section 6.1.1, the lowest order information bit of the SIB.Data field is mapped to the most significant bit of the SIB1 transport block.

    • For subframe 5, per TS 36.101 [1], Annex A.3, reference PDSCH transmissions are not scheduled in subframe 5 except for the SIB1 associated PDSCH.

    • Setting the OCNG parameter field 'On' fills all unused, unscheduled PDSCH resource elements with QPSK modulated random data.

    • The values for CFI and PRBSet can vary per subframe. If these parameters are arrays, then the function cyclically steps through the elements of the array starting with the index given by mod(NSubframe,length(parameter)). When parameter is PRBSet, the parameter must be a cell array of column vectors or slot-wise matrices.

    • The PHICH symbols carry a single ACK on the first PHICH instance in each PHICH group.

OCNGPDSCH substructure

The substructure, OCNGPDSCH, defines the OCNG patterns in associated RMCs and tests according to TS 36.101 [1], Section A.5. OCNGPDSCH contains these fields which can also be customized with the full range of PDSCH-specific values.

Parameter FieldValuesDescription
Modulation

OCNG Modulation has same setting options as rmccfgout.PDSCH.Modulation

See rmccfgout.PDSCH.Modulation

TxScheme

OCNG TxScheme has same setting options as rmccfgout.PDSCH.TxScheme

See rmccfgout.PDSCH.TxScheme

RNTI

0 (default), scalar integer

OCNG radio network temporary identifier (RNTI) value. (16 bits)

Data Types: struct

More About

collapse all

DL Reference Channel Options

The output configuration structure is initialized in accordance with the reference channels defined in TS 36.101, Annex A.3. Initialization choices available for the downlink reference channel and associated top-level configuration defaults include:

Reference channelsReference channels (continued)

R.0 (Port0, 1 RB, 16QAM, CellRefP=1, R=1/2)

R.1 (Port0, 1 RB, 16QAM, CellRefP=1, R=1/2)

R.2 (Port0, 50 RB, QPSK, CellRefP=1, R=1/3)

R.3 (Port0, 50 RB, 16QAM, CellRefP=1, R=1/2)

R.4 (Port0, 6 RB, QPSK, CellRefP=1, R=1/3)

R.5 (Port0, 15 RB, 64QAM, CellRefP=1, R=3/4)

R.6 (Port0, 25 RB, 64QAM, CellRefP=1, R=3/4)

R.7 (Port0, 50 RB, 64QAM, CellRefP=1, R=3/4)

R.8 (Port0, 75 RB, 64QAM, CellRefP=1, R=3/4)

R.9 (Port0, 100 RB, 64QAM, CellRefP=1, R=3/4)

R.10 (TxDiversity|SpatialMux, 50 RB, QPSK, CellRefP=2, R=1/3)

R.11 (TxDiversity|SpatialMux|CDD, 50 RB, 16QAM, CellRefP=2, R=1/2)

R.12 (TxDiversity, 6 RB, QPSK, CellRefP=4, R=1/3)

R.13 (SpatialMux, 50 RB, QPSK, CellRefP=4, R=1/3)

R.14 (SpatialMux|CDD, 50 RB, 16QAM, CellRefP=4, R=1/2)

R.25 (Port5, 50 RB, QPSK, CellRefP=1, R=1/3)

R.26 (Port5, 50 RB, 16QAM, CellRefP=1, R=1/2)

R.27 (Port5, 50 RB, 64QAM, CellRefP=1, R=3/4)

R.28 (Port5, 1 RB, 16QAM, CellRefP=1, R=1/2)

R.31-3A FDD (CDD, 50 RB, 64QAM, CellRefP=2, R=0.85-0.90)

R.31-3A TDD (CDD, 68 RB, 64QAM, CellRefP=2, R=0.87-0.90)

R.31-4 (CDD, 100 RB, 64QAM, CellRefP=2, R=0.87-0.90)

R.43 FDD (Port7-14, 50 RB, QPSK, CellRefP=2, R=1/3)

R.43 TDD (SpatialMux, 100 RB, 16QAM, CellRefP=4, R=1/2)

R.44 FDD (Port7-14, 50 RB, QPSK, CellRefP=2, R=1/3)

R.44 TDD (Port7-14, 50 RB, 64QAM, CellRefP=2, R=1/2)

R.45 (Port7-14, 50 RB, 16QAM, CellRefP=2, R=1/2)

R.45-1 (Port7-14, 39 RB, 16QAM, CellRefP=2, R=1/2)

R.48 (Port7-14, 50 RB, QPSK, CellRefP=2, R=1/2)

R.50 FDD (Port7-14, 50 RB, 64QAM, CellRefP=2, R=1/2)

R.50 TDD (Port7-14, 50 RB, QPSK, CellRefP=2, R=1/3)

R.51 (Port7-14, 50 RB, 16QAM, CellRefP=2, R=1/2)

R.6-27RB (Port0, 27 RB, 64QAM, CellRefP=1, R=3/4)

R.12-9RB (TxDiversity, 9 RB, QPSK, CellRefP=4, R=1/3)

R.11-45RB (CDD, 45 RB, 16QAM, CellRefP=2, R=1/2)

    Note:   Reference channels 'R.6-27RB', 'R.12-9RB', and 'R.11-45RB' maintain the same code rate as the standard versions but are custom RMCs configured for nonstandard bandwidths.

References

[1] 3GPP TS 36.101. "User Equipment (UE) radio transmission and reception." 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA). URL: http://www.3gpp.org.

[2] 3GPP TS 36.211. "Physical channels and modulation." 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA). URL: http://www.3gpp.org.

[3] 3GPP TS 36.212. "Multiplexing and channel coding." 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA). URL: http://www.3gpp.org.

[4] 3GPP TS 36.213. "Physical layer procedures." 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA). URL: http://www.3gpp.org.

[5] 3GPP TS 36.321. "Medium Access Control (MAC) protocol specification." 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA). URL: http://www.3gpp.org.

Introduced in R2014a

Was this topic helpful?