umtsDownlinkWaveformGenerator

UMTS downlink waveform generation

Syntax

waveform = umtsDownlinkWaveformGenerator(config)

Description

waveform = umtsDownlinkWaveformGenerator(config) returns the Universal Mobile Telecommunications Service (UMTS) downlink waveform, waveform, defined by the configuration structure, config. This function supports Wideband Code Division Multiple Access (W-CDMA), High-Speed Downlink Packet Access (HSDPA), and Evolved High-Speed Packet Access (HSPA+) waveform generation. The top-level parameters and lower-level substructures of config characterize the waveform and channel properties of the umtsDownlinkWaveformGenerator function output. The config input is generated using the umtsDownlinkReferenceChannels function; config includes top-level parameters and substructures to describe the different channels to include in the waveform. The top-level parameters of config are: TotFrames, PrimaryScramblingCode, FilterType, OversamplingRatio, and NormalizedPower. To enable the specific channels, you can add associated substructures: DPCH, PCCPCH, SCCPCH, PCPICH, SCPICH, PSCH, SSCH, PICH, HSDPA, and OCNS.

Note

Include an interfering downlink W-CDMA noise source by initializing the OCNS substructure. Specify the orthogonal channel noise source (OCNS) parameters using the appropriate 3GPP definition,

RMC OCNS channels are defined in TS 25.101, Table C.6 [1]
H-Set OCNS channels are defined in TS 25.141, Tables C.13, and C.13A [2]
Test model DPCHs and HS-PDSCH/HS-SCCH channels are defined in TS 25.141, Section 6.1.1 [2]

example

Examples

collapse all

UMTS Downlink Waveform Generation

Open Script

Initialize a 'QPSK', 'H-Set1' FRC reference channel and generate the UMTS waveform that corresponds to these settings.

Generate the configuration structure, frcStruct.

rc = 'H-Set1';
modulation = 'QPSK';
frcStruct = umtsDownlinkReferenceChannels(rc, modulation);

Generate the desired waveform using frcStruct as the input to the waveform generation function. Create a spectrum analyzer object sampling at chiprate x OversamplingRatio. Plot the waveform.

waveform = umtsDownlinkWaveformGenerator(frcStruct);
saScope = spectrumAnalyzer(SampleRate=3.84e6*frcStruct.OversamplingRatio);
saScope(waveform);

Input Arguments

collapse all

`config` — Definition of the channels included by waveform generator
structure

Top-Level Parameters and Substructures

Definition of the channels included by the waveform generator, specified as a structure.

Parameter Field	Required or Optional	Values	Description
`TotFrames`	Required	Nonnegative integer	Total number of 10 ms frames to be generated, specified as a nonnegative integer. The default is 1.
`PrimaryScramblingCode`	Required	Nonnegative integer	Primary scrambling code index, specified as a nonnegative integer in the interval [0, 511].
`FilterType`	Required	`'RRC'` (default), `'Off'`	Enable or disable the RRC filter by setting `FilterType` to `'RRC'` or `'off'`. respectively.
`OversamplingRatio`	Required	Nonnegative integer	Oversampling ratio, specified as a nonnegative integer.
`NormalizedPower`	Required	Float, `–inf`, `inf`,`'Off'`	Overall waveform power in dBW relative to 1 ohm, specified as a float, –`inf`, `inf`, or `'Off'`. Setting `NormalizedPower` to `'Off'` disables power normalization.
`DPCH`	Optional	Not present, structure, or structure array	See DPCH Substructure.
`PCCPCH`	Optional	Not present or structure	See PCCPCH Substructure.
`SCCPCH`	Optional	Not present or structure	See SCCPCH Substructure.
`PCPICH`	Optional	Not present or structure	See PCPICH Substructure.
`SCPICH`	Optional	Not present or structure	See SCPICH Substructure.
`PSCH`	Optional	Not present or structure	See PSCH Substructure.
`SSCH`	Optional	Not present or structure	See SSCH Substructure.
`PICH`	Optional	Not present or structure	See PICH Substructure.
`HSDPA`	Optional	Not present or structure	See HSDPA Substructure.
`OCNS`	Optional	Not present or structure	See OCNS Substructure.

DPCH Substructure

To add dedicated physical channels (DPCHs) to the output structure, include the DPCH substructure in the config structure. The DPCH substructure contains the following fields.

Parameter Field	Required or Optional	Values	Description
`Enable`	Required	`'On'`, `'Off'`	Enable or disable the channel by setting `Enable` to `'On'` or `'Off'`, respectively.
`SlotFormat`	Required	Nonnegative integer	DPCH slot format number, specified as a nonnegative integer in the interval [0, 16].
`SpreadingCode`	Required	Nonnegative integer	DPCH spreading code, specified as a nonnegative integer in the interval [0, 512]. For multicode transmission, `SpreadingCode` is the first DPCH code.
`NMulticodes`	Required	Positive integer	Number of DPCHs, specified as 1, 2, 3, 4, 5, or 6.
`SecondaryScramblingCode`	Required	Nonnegative integer	DPCH secondary scrambling code index, specified as a nonnegative integer in the interval [0, 15].
`TimingOffset`	Required	Nonnegative integer	The timing offset in terms of the number of chips (x256Tchip), specified as a nonnegative integer in the interval [0, 149].
`Power`	Required	Float, `–inf`, `inf`	Channel power in dB, specified as a float, `–inf`, or `inf`.
`TPCData`	Required	Binary scalar, binary vector	Transmit Power Control data, specified as a binary scalar or a vector with binary entries.
`TFCI`	Required	Nonnegative integer	Transport Format Combination Indicator (TFCI), specified as a nonnegative integer in the interval [0, 1023].
`DataSource`	Required	Binary scalar, binary vector, character vector, cell array, or string scalar	DPCH data source, specified as a binary scalar, a vector with binary entries, a character vector, a cell array, or a string scalar. When specifying `DataSource` as a cell array, use standard PN sequences and a seed value: {PN, seed}. PN options for character vector or cell array are `'PN9-ITU'`, `'PN9'`, `'PN11'`, `'PN15'`, and `'PN23'`. If no seed is specified, the shift register is initialized with all ones. To enable transport channel coding, specify `DataSource` as `'CCTrCH'`.
`CCTrCH`	Optional	Structure	See CCTrCH Substructure.

CCTrCH Substructure

Include a CCTrCH substructure instance individually for DPCH, PCCPCH, and/or SCCPCH substructures. Separate instances of a coded composite transport channel (CCTrCH) are added to the output structures of the DPCH, P-CCPCH, and/or S-CCPCH physical channel definitions. When the CCTrCH substructure is included, it contains the following fields.

Parameter Field	Required or Optional	Values	Description
`Name`	Optional	Character vector, string scalar Default depends on the physical channel specified	Name assigned to the CCTrCH, specified as a character vector or a string scalar. Functions do not use the `Name` field. Therefore, you can redefine the content with no consequence.
`DTXPosition`	Required	`'fixed'`, `'flexible'`	Specifies the DTX position, specified as `'fixed'` or `'flexible'`.
`TrCH`	Required	Structure, structure array	Transport channels in the CCTrCH, specified as a structure or a structure array.
`TrCH.Name`	Required	Character vector, string scalar Default depends on the physical channel specified	Name assigned to the TrCH, specified as a character vector or a string scalar. Functions do not use the `Name` field. Therefore, you can redefine the content with no consequence.
`TrCH.CRC`	Required	Character vector, string scalar	Cyclic redundancy check (CRC) polynomial specifier, specified as one of these values: `'0'`, `'8'`, `'12'`, `'16'`, or `'24'`.
`TrCH.TTI`	Required	Positive integer	Transmission time interval (TTI) in milliseconds, specified as 10, 20, 40, or 80.
`TrCH.CodingType`	Required	`'turbo'`, `'conv2'`, `'conv3'`	Channel coding type and rate, specified as `'turbo'`, `'conv2'`, or `'conv3'`.
`TrCH.RMA`	Required	Positive integer	Rate matching attribute value, specified as a positive integer in the interval [1, 256].
`TrCH.DataSource`	Required	Binary scalar, binary vector, character vector, cell array, or string scalar	Transport channel data source, specified as a binary scalar, a vector with binary entries, a cell array, or a string scalar. When defined as a cell array use standard PN sequences and a seed value: {PN, seed}. PN options for character vector or cell array are `'PN9-ITU'`, `'PN9'`, `'PN11'`, `'PN15'`, and `'PN23'`. If no seed is specified, the shift register is initialized with all ones.
`TrCH.DataSource`	Required	Examples for setting the `DataSource` field include: ...`CCTrCH.TrCh(1).DataSource = [1 0 0 1]` generates a sequence of transport blocks by looping the vector [1 0 0 1]. ...`CCTrCH.TrCh(1).DataSource = 'PN9'` generates a transport channel data block with random seed = 511. ...`CCTrCH.TrCh(1).DataSource = {'PN9',5}` generates a transport channel data block with seed = 5.
`TrCH.ActiveDynamicPart`	Required	Positive integer, vector	Active dynamic part, specified as a positive integer or a vector whose entries are positive integers in the interval [1, `length(DynamicPart)`].
`TrCH.ActiveDynamicPart`	Required	The `ActiveDynamicPart` field indicates the `DynamicPart` array index for the active transport format `(BlockSize, BlockSetSize)` from available combinations defined in `DynamicPart`. The selected transport format is used for data transmission in the current TTI.
`TrCH.DynamicPart`	Required	Structure, structure array	Size of each transport block, specified as a structure or a structure array.
`TrCH.DynamicPart`	Required	The `DynamicPart` fields, `BlockSize` and `BlockSetSize`, define the size of each transport block and the total bits per transport block set. As a pair `(BlockSize, BlockSetSize)` describe a transport format set. `DynamicPart` defines one or multiple transport format sets.
`TrCH.DynamicPart.BlockSize`	Required	Positive integer	Transport block length, specified as a positive integer.
`TrCH.DynamicPart.BlockSetSize`	Required	Integer, multiple of `BlockSize`	Total number of bits in the transport block set. Implementation does not support multiple transport blocks, so by definition `BlockSize` is equal to `BlockSetSize`.

Note

When configuring the output structure to transmit the RMC 0kbps as defined in TS 25.101, Section A.3.0 [1], a transport channel CRC is defined for transmission. The standard indicates DTCH transport block size = 0 and transport block set size = 0. Our implementation requires signaling transmission of a transport block to transmit a CRC. In the umtsDownlinkWaveformGenerator, one transport block of size zero is signaled by setting either BlockSize or BlockSetSize to '0'. Setting both BlockSize and BlockSetSize to '0' signals '0' transport block of size '0' and no CRC is transmitted.

PCCPCH Substructure

To add the primary common control physical channel (PCCPCH) to the output structure, include the PCCPCH substructure in the config structure. The PCCPCH substructure contains the following fields.

Parameter Field	Required or Optional	Values	Description
`Enable`	Required	`'On'`, `'Off'`	Enable or disable the channel by specifying `Enable` as `'On'` or `'Off'`, respectively.
`Power`	Required	Float, `–inf`, `inf`	PCCPCH power in dB, specified as a float, -`inf`, or `inf`.
`DataSource`	Required	Binary scalar, binary vector, character vector, cell array, or string scalar	PCCPCH data source, specified as a binary scalar, a vector with binary entries, a character vector, a cell array, or a string scalar. When specifying `DataSource` as a cell array, use standard PN sequences and a seed value: {PN, seed}. PN options for character vector or cell array are `'PN9-ITU'`, `'PN9'`, `'PN11'`, `'PN15'`, and `'PN23'`. If no seed is specified, the shift register is initialized with all ones. To enable BCH transport channel coding, specify `DataSource` as `'CCTrCH'`.
`CCTrCH`	Optional	Structure	See `CCTrCH` Substructure.

SCCPCH Substructure

To add the secondary common control physical channel (SCCPCH) to the output structure, include the SCCPCH substructure in the config structure. The SCCPCH substructure contains the following fields.

Parameter Field	Required or Optional	Values	Description
`Enable`	Required	`'On'`, `'Off'`	Enable or disable the channel by specifying `Enable` as `'On'` or `'Off'`, respectively.
`SlotFormat`	Required	Nonnegative integer	SCCPCH slot format number, specified as a nonnegative integer in the interval [0, 17].
`SpreadingCode`	Required	Nonnegative integer Valid range depends on slot format	SCCPCH spreading code, specified as a nonnegative integer in the interval [0, 255].
`SecondaryScramblingCode`	Required	Nonnegative integer	SCCPCH secondary scrambling code index, specified as a nonnegative integer in the interval [0, 15].
`TimingOffset`	Required	Nonnegative integer	Timing offset in terms of the number of chips (x256Tchip), specified as a nonnegative integer in the interval [0, 149].
`Power`	Required	Float, -`inf`, `inf`	SCCPCH power in dB, specified as a float, -`inf`, or `inf`.
`TFCI`	Required	Nonnegative integer	Transport format combination indicator, specified as a nonnegative integer in the interval [0, 1023].
`DataSource`	Required	Scalar, vector, character vector, cell array, or string scalar	SCCPCH data source, specified as a binary scalar, a vector with binary entries, a character vector, a cell array, or a string scalar. When defined as a cell array use standard PN sequences and a seed value: {PN, seed}. PN options for character vector or cell array are `'PN9-ITU'`, `'PN9'`, `'PN11'`, `'PN15'`, and `'PN23'`. If no seed is specified, the shift register is initialized with all ones. To enable PCH/FACH transport channel coding, specify `DataSource` as `'CCTrCH'`.
`CCTrCH`	Optional	Structure	See `CCTrCH` Substructure.

PCPICH Substructure

To add the primary common pilot channel to the output structure, include the PCPICH substructure in the config structure. The PCPICH substructure contains the following fields.

Parameter Field	Required or Optional	Values / Ranges / Notes	Description
`Enable`	Required	`'On'`, `'Off'`	Enable or disable the channel by specifying `Enable` as `'On'` or `'Off'`, respectively.
`Power`	Required	Float, –`inf`, `inf`	PCPICH power in dB, specified as a float, –`inf`, or `inf`.

SCPICH Substructure

To add the secondary common pilot channel (SCPICH) to the output structure, include the SCPICH substructure in the config structure. The SCPICH substructure contains the following fields.

Parameter Field	Required or Optional	Values	Description
`Enable`	Required	`'On'`, `'Off'`	Enable or disable the channel by specifying `Enable` as `'On'` or `'Off'`, respectively.
`SpreadingCode`	Required	Nonnegative integer	SCPICH spreading code, specified as a nonnegative integer in the interval [0, 255].
`SecondaryScramblingCode`	Required	Nonnegative integer	SCPICH secondary scrambling code index, specified as a nonnegative integer in the interval [0, 15].
`Power`	Required	Float, –`inf`, `inf`	SCPICH power in dB, specified as a float, –`inf`, or `inf`.

PSCH Substructure

To add the physical shared channel (PSCH) to the output structure, include the PSCH substructure in the config structure. The PSCH substructure contains the following fields.

Parameter Field	Required or Optional	Values	Description
`Enable`	Required	`'On'`, `'Off'`	Enable or disable the channel by specifying `Enable` as `'On'` or `'Off'`, respectively.
`Power`	Required	Float, –`inf`, `inf`	PSCH power in dB, specified as a float, –`inf`, or `inf`.

SSCH Substructure

To add the secondary synchronization channel (SSCH) to the output structure, include the SSCH substructure in the config structure. The SSCH substructure contains the following fields.

Parameter Field	Required or Optional	Values	Description
`Enable`	Required	`'On'`, `'Off'`	Enable or disable the channel by specifying `Enable` as `'On'` or `'Off'`, respectively.
`Power`	Required	Float, –`inf`, `inf`	SSCH power in dB, specified as a float, –`inf`, or `inf`.

PICH Substructure

To add the page indicator channel (PICH) to the output structure, include the PICH substructure in the config structure. The PICH substructure contains the following fields.

Parameter Field	Required or Optional	Values	Description
`Enable`	Required	`'On'`, `'Off'`	Enable or disable the channel by specifying `Enable` as `'On'` or `'Off'`, respectively.
`SpreadingCode`	Required	Nonnegative integer	PICH spreading code, specified as a nonnegative integer in the interval [0, 255].
`TimingOffset`	Required	Nonnegative integer	Timing offset in terms of the number of chips (x256Tchip), specified as a nonnegative integer in the interval [0, 149].
`Power`	Required	Float, –`inf`, `inf`	PICH power in dB, specified as a float, –`inf`, or `inf`.
`DataSource`	Required	Scalar, vector, character vector, cell array, or string scalar	PICH data source, specified as a binary scalar, a vector with binary entries, a character vector, a cell array, or a string scalar. When defined as a cell array use standard PN sequences and a seed value: {PN, seed}. PN options for character vector or cell array are `'PN9-ITU'`, `'PN9'`, `'PN11'`, `'PN15'`, and `'PN23'`. If no seed is specified, the shift register is initialized with all ones. To use paging data, specify `DataSource` as `'PagingData'`.
`Np`	Required	Positive integer	Number of paging indicators per frame, specified as one of the values 18, 36, 72, 144.

HSDPA Substructure

To add high-speed downlink packet access (HSDPA) information and channels to the output structure, include the HSDPA substructure in the config structure. The HSDPA substructure contains the following fields.

Parameter Field	Required or Optional	Values / Ranges / Notes	Description
`Enable`	Required	`'On'`, `'Off'`	Enable or disable the HSDPA channels (HS-PDSCHs and HS-SCCH) by specifying `Enable` as `'On'` or `'Off'`, respectively.
`CodeGroup`	Required	Positive integer	Number of channelization codes used simultaneously for HS-PDSCHs, specified as a positive integer in the interval [1, 16].
`CodeOffset`	Required	Nonnegative integer	Offset to the first channelization code to use for HS-PDSCHs, specified as a nonnegative integer in the interval [0, 15].
`Modulation`	Required	`'QPSK'`, `'16QAM'`, `'64QAM'`	Symbol modulation, specified as one of the values `'QPSK'`, `'16QAM'`, or `'64QAM'`.
`VirtualBufferCapacity`	Required	Positive integer	Number of soft channel bits (or soft metric location) in a HARQ process for the H-Sets as defined in TS 36.101 Annex A.7. Specify `VirtualBufferCapacity` as a positive integer. The number of soft channel bits depends on the UE category as specified in TS 25.306 Section 5.1. The value of this parameter must match the number of soft channel bits in a HARQ process used in the test device or decoding software.
`InterTTIDistance`	Required	Positive integer	Transmission time interval in subframes. This interval is the distance between different HARQ transmissions to the same UE. A value of 1 indicates continuous HSDPA transmissions in every subframe to the UE under test. A value larger than 1 indicates the presence of gap subframes with no data transmission to the UE under test.
`NHARQProcesses`	Required	Positive integer	Total number of HARQ processes, specified as a positive integer in the interval [1, 8].
`XrvSequence`	Required	Nonnegative integer, vector of nonnegative integers	Redundancy and constellation version coding sequence, specified as a nonnegative integer, or a vector whose entries are nonnegative integers, in the interval [0, 7]. `XrvSequence` encodes the redundancy version parameters (r,s) and constellation version as defined in TS 25.212 Section 4.6. The encoding includes the constellation version only if the modulation scheme is 16QAM/64QAM. The values are used by each HARQ process for each transmission. A scalar indicates a single transmission. A vector indicates retransmissions. The new data indicator bit signalled by HS-SCCH stays the same and the redundancy version changes to the value encoded in the next element of `XrvSequence`. When a HARQ process completes all transmissions corresponding to the `XrvSequence`, the new data indicator bit toggles between 0 and 1 indicating a new transmission. For more information, see TS 25.321 Section 11.6.1.3. For sequences used for HSDPA H-Sets, see TS 25.101 Section 9.
`UEId`	Required	Nonnegative integer	UE identity, specified as a nonnegative integer in the interval [0, 2¹⁶ – 1].
`TransportBlockSizeId`	Required	Nonnegative integer	Transport block size index (x_tbs) signaled on the HS-SCCH as defined in TS 25.212 Section 4.6. The calculation is based on the `HSDSCH.BlockSize` parameter used for transmission as defined in TS 25.321 Section 9.2.3 Annex A. Specify `TransportBlockSizeID` as a nonnegative integer in the interval [0, 63].
`HSSCCHSpreadingCode`	Required	Nonnegative integer	HS-SCCH spreading code, specified as a nonnegative integer in the interval [0, 127].
`SecondaryScramblingCode`	Required	Nonnegative integer	Secondary scrambling code index for HS-PDSCH and HS-SCCH channels, specified as a nonnegative integer in the interval [0, 15].
`HSPDSCHPower`	Required	Float, –`inf`, `inf`	HS-PDSCH power in dB, specified as a float, –`inf`, or `inf`.
`HSSCCHPower`	Required	Float`inf`, `inf`	HS-SCCH power in dB, specified as a float, –`inf`, or `inf`.
`DataSource`	Required	Scalar, vector, character vector, cell array, or string scalar	HSDPA data source, specified as a binary scalar, a vector with binary entries, a character vector, a cell array, or a string scalar. When specifying `DataSource` as a cell array, use standard PN sequences and a seed value in the form {PN, seed}. PN options for character vector or cell array are `'PN9-ITU'`, `'PN9'`, `'PN11'`, `'PN15'`, and `'PN23'`. If no seed is specified, the shift register is initialized with all ones. To enable HS-DSCH transport channel coding, specify `DataSource` as `'HSDSCH'`.
`HSDSCH`	Optional	Not present or a structure	HS-DSCH transport channel configuration, specified as a structure.
The following fields are required only if the `HSDSCH` substructure is present.
`HSDSCH.BlockSize`	Required	Nonnegative integer	Transport block size, specified as a nonnegative integer.
`HSDSCH.DataSource`	Required	Scalar, vector, character vector, cell array, or string scalar	HS-DSCH transport data source, specified as a binary scalar, a vector with binary entries, a cell array, or a string scalar. When defined as a cell array use standard PN sequences and a seed value: {PN, seed}. PN options for character vector or cell array are `'PN9-ITU'`, `'PN9'`, `'PN11'`, `'PN15'`, and `'PN23'`. If no seed is specified, the shift register is initialized with all ones.

In the generator, the HSPDA functionality creates continuous HS-PDSCH and HS-SCCH transmissions. This functionality supports the HSPDA H-Set fixed reference channels where a multi-HARQ reference transmission sequence is defined. The multi-HARQ reference transmission sequence is masked with the same RNTI, directed at a single UE specified by the UEId parameter. The NHARQProcesses and InterTTIDistance parameters define the reference transmission frequency to the UE. Any gaps between the reference subframes are filled with additional HS-PDSCH/HS-SCCH subframes. These subframes are masked with a complementary RNTI, directed at a different UE defined as xor(UEId,65535). The NHARQProcesses parameter gives the numbers of HARQ processes used in the reference transmission. The number of gap subframes between each transport block transmission or retransmission for different HARQ processes is InterTTIDistance-1. Due to the HARQ ACK-NACK feedback signaling requirements, the gap between the transmissions of the same HARQ process should be no less than six subframes.

The HSDPA.DataSource parameter controls the data transmitted on the reference PDSCH and HS-SCCH physical channels. If HSDPA.DataSource is set to 'HSDSCH', the reference PDSCH data comes from an HS-DSCH transport channel and the HS-SCCH channel carries the associated control information. In this case, the source to the HS-DSCH transport channel is parameterized by the fields in the HSDSCH substructure data (transport block size and data stream). This reference data is also used to fill the non-reference gap subframes:

The gap HS-PDSCH subframes are filled with the same HS-DSCH encoded data used for reference transmission. The encoded data is scrambled according to the subframe.
The gap HS-SCCH subframes are filled with the encoded control information using the complimentary RNTI.

The HS-SCCH transmission is aligned with the scrambling boundary. The HS-PDSCH transmission begins 2×Tslot = 5120 chips after the start of the HS-SCCH (see TS 25.211 Section 7.8). To fill the first two slots in the generated waveform, the HS-PDSCH wraps around for the last subframe.

The virtualBufferCapacity parameter must match the number of soft channel bits in a HARQ process used in the test device or decoding software.

OCNS Substructure

To add orthogonal channel noise source (OCNS) information to the output structure, include the OCNS substructure in the config structure. The OCNS substructure contains the following fields.

Parameter Field

Required or Optional

Values

Description

Enable

Required

'On', 'Off'

Enable or disable the channel by specifying Enable as 'On' or 'Off', respectively.

Power

Required

Float, –inf, or inf

OCNS overall power in dB, specified as a float, -inf, or inf.

OCNSType

Required

Character vector or string scalar

If OCNS is enabled, OCNSType specifies which OCNS configuration to use. The OCNS substructure and OCNSType field are used to generate:

DPCHs, defined as OCNS channels in TS 25.101.
DPCHs, HS-PDSCHs, and HS-SCCHs, defined for test models in TS 25.141, Section 6.
For RMCs and H-Sets, specify OCNSType as one of these values: 'RMC_16DPCH', 'H-Set_6DPCH', 'H-Set_4DPCH'
For Test Model DPCH and HS-PDSCH/HS-SCCH sets, specify OCNSType as one of these values: 'TM1_4DPCH', 'TM1_8DPCH', 'TM1_16DPCH', 'TM1_32DPCH', 'TM1_64DPCH', 'TM2_3DPCH', 'TM3_4DPCH', 'TM3_8DPCH', 'TM3_16DPCH', 'TM3_32DPCH', 'TM5_4DPCH_4HSPDSCH', 'TM5_6DPCH_2HSPDSCH', 'TM5_14DPCH_4HSPDSCH', 'TM5_30DPCH_8HSPDSCH', 'TM6_4DPCH_4HSPDSCH', 'TM6_30DPCH_8HSPDSCH'.

For test model generation, set the corresponding channel configuration Enable field to 'Off'.

Output Arguments

collapse all

`waveform` — Modulated baseband waveform containing the UMTS physical channels
complex vector array

Modulated baseband waveform containing the UMTS physical channels, returned as a complex vector array, sampled at (3.84 × config.OversamplingRatio) MHz.

Data Types: double
Complex Number Support: Yes

References

[1] 3GPP TS 25.101. “Universal Mobile Telecommunications System (UMTS); User Equipment (UE) Radio Transmission and Reception (FDD).” 3rd Generation Partnership Project; Technical Specification Group Radio Access Network. URL: https://www.3gpp.org.

[2] 3GPP TS 25.141. “Universal Mobile Telecommunications System (UMTS); Base Station (BS) Conformance Testing (FDD).” 3rd Generation Partnership Project; Technical Specification Group Radio Access Network. URL: https://www.3gpp.org.

[3] 3GPP TS 25.211. “Universal Mobile Telecommunications System (UMTS); Physical channels and mapping of transport channels onto physical channels (FDD).” 3rd Generation Partnership Project; Technical Specification Group Radio Access Network. URL: https://www.3gpp.org.

[4] 3GPP TS 25.212. “Universal Mobile Telecommunications System (UMTS); Multiplexing and channel coding (FDD).” 3rd Generation Partnership Project; Technical Specification Group Radio Access Network. URL: https://www.3gpp.org.

[5] 3GPP TS 25.306. “Universal Mobile Telecommunications System (UMTS); UE Radio Access capabilities.” 3rd Generation Partnership Project; Technical Specification Group Radio Access Network. URL: https://www.3gpp.org.

[6] 3GPP TS 25.321. “Universal Mobile Telecommunications System (UMTS); Medium Access Control (MAC) protocol specification.” 3rd Generation Partnership Project; Technical Specification Group Radio Access Network. URL: https://www.3gpp.org.

[7] 3GPP TS 36.101. “Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) Radio Transmission and Reception.” 3rd Generation Partnership Project; Technical Specification Group Radio Access Network. URL: https://www.3gpp.org.

Version History

Introduced in R2015a

umtsDownlinkWaveformGenerator

Syntax

Description