## Syntax

``config = umtsUplinkReferenceChannels(rc)``

## Description

example

````config = umtsUplinkReferenceChannels(rc)` returns a structure containing the configuration parameters for the UMTS uplink reference channel defined by `rc`. The output structure, `config`, contains the configuration parameters required by `umtsUplinkWaveformGenerator` to generate an uplink reference channel waveform. `umtsUplinkReferenceChannels` uses, `rc`, to initialize a configuration data structure that is compliant with one of the reference channels defined in the following 3GPP standards:Uplink RMC configurations are defined in TS 25.101, Annex A.2 [1].Uplink E-DPDCH FRC configurations are as defined in TS 25.141, Annex 10 [2].```

## Examples

collapse all

Initialize a `'RMC12.2kbps'` reference channel.

Generate the configuration structure, `config`.

```rc = 'RMC12.2kbps'; config = umtsUplinkReferenceChannels(rc);```

The output from `umtsUplinkReferenceChannels` provides the input required to generate the desired UMTS waveform corresponding to these settings.

Examine the `DPDCH` field in `config`. This field uses a nested structure to define this physical channel for the `'RMC12.2kbps'` reference channel.

`config`
```config = struct with fields: TotFrames: 1 ScramblingCode: 1 FilterType: 'RRC' OversamplingRatio: 4 NormalizedPower: 'Off' DPDCH: [1x1 struct] DPCCH: [1x1 struct] HSUPA: [1x1 struct] HSDPCCH: [1x1 struct] ```
`config.DPDCH`
```ans = struct with fields: Enable: 'On' SlotFormat: 2 CodeCombination: 64 Power: 0 DataSource: 'CCTrCH' CCTrCH: [1x1 struct] ```
`config.DPDCH.CCTrCH`
```ans = struct with fields: Name: 'DCH' TrCH: [1x2 struct] ```
`config.DPDCH.CCTrCH.TrCH(1)`
```ans = struct with fields: Name: 'DTCH' CRC: '16' CodingType: 'conv3' RMA: 256 TTI: 20 DataSource: 'PN9-ITU' ActiveDynamicPart: 1 DynamicPart: [1x1 struct] ```
`config.DPDCH.CCTrCH.TrCH(1).DynamicPart`
```ans = struct with fields: BlockSize: 244 BlockSetSize: 244 ```
`config.DPDCH.CCTrCH.TrCH(2)`
```ans = struct with fields: Name: 'DCCH' CRC: '12' CodingType: 'conv3' RMA: 256 TTI: 40 DataSource: 'PN9-ITU' ActiveDynamicPart: 1 DynamicPart: [1x1 struct] ```
`config.DPDCH.CCTrCH.TrCH(2).DynamicPart`
```ans = struct with fields: BlockSize: 100 BlockSetSize: 100 ```

## Input Arguments

collapse all

Reference channel configuration, specified as a character vector or string scalar. `rc` identifies which RMC or E-DPDCH FRC to configure. Values for `rc` when specified as a character vector include (for string scalar use double quotes):

Parameter FieldRequired or OptionalValuesDescription
`rc`Required

Reference measurement channels:

`'RMC12.2kbps'`, `'RMC64kbps'`, `'RMC144kbps'`, `'RMC384kbps'`

Reference channel identifying the W-CDMA uplink RMC configuration set-up as defined in TS 25.101, Annex A.2 [1].

E-DPDCH Fixed Reference Channels:

`'FRC1'`, `'FRC2'`, `'FRC3'`, `'FRC4'`, `'FRC5'`, `'FRC6'`, ` 'FRC7'`, `'FRC8'`

Reference channel identifying the E-DPDCH FRC configuration as defined in TS 25.141, Annex A.10 [2].

Note

Additional standards-based reference channels can be configured by executing `lteUplinkReferenceChannels` and then adjusting parameters to match configurations defined in TS 25.141 [2]. For example:

• To generate the HS-DPCCH RMC, use` 'RMC12.2kbps'` and set `HSDPCCH.Enable = 'On'`.

• To generate the 12.2 kbps RMC defined in TS 25.141 [2], use ` 'RMC12.2kbps'`. Using this value the function initializes `config` to generate the TS 25.101 [1] 12.2 kbps RMC). After `config` is generated, adjust the DPDCH and DPCCH parameters to align with the settings in TS 25.141 [2].

Data Types: `char` | `string`

## Output Arguments

collapse all

#### Top-Level Parameters and Substructures

Definition of the channels included for the waveform generator, returned as a structure.

Parameter Field

Required or Optional

Values

Description

`TotFrames`Required

Positive scalar integer

Total number of frames to be generated

`ScramblingCode`Required

Scalar integer

`$0-\left({2}^{24}-1\right)$`

Scrambling code index used by UE

`FilterType`Required`'RRC'`, or `'Off'`

Enable the RRC filter

`OversamplingRatio`Required

Positive scalar integer

Oversampling ratio

`NormalizedPower`Required

Float (-inf to +inf) or `'Off'` to disable power normalization

Overall waveform power in dBW relative to 1 ohm

`DPDCH`Optional

Not present or single structure

See DPDCH Substructure.
`DPCCH`Optional

Not present or single structure

See DPCCH Substructure.
`HSUPA`Optional

Not present or single structure

See HSUPA Substructure.
`HSDPCCH`Optional

Not present or single structure

See HSDPCCH Substructure.

#### DPDCH Substructure

Include the `DPDCH` substructure in the `config` structure to add the dedicated physical data channel to the output structure. The `DPDCH` 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

DPDCH slot format number, specified as 0, 1, 2, 3, 4, 5, or 6.

`CodeCombination`Required

Nonnegative integer, vector

Valid spreading factors, specified as a power of two or a vector of powers of two in the interval [4, 256].

`Power`Required

Float, –`inf`, `inf`

Channel power in dB, specified as a float, –`inf`, or `inf`.

`DataSource`Required

Scalar, vector, character vector, cell array, string scalar

DPDCH data source, specified as a scalar, vector, cell array, or 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 transport channel coding, specify `DataSource` as `'CCTrCH'`.

`CCTrCH`Optional

Structure

See CCTrCH Substructure.

#### CCTrCH Substructure

The `CCTrCH` substructure is associated with the DPDCH physical channel definition substructures. The `CCTrCH` substructure 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.

`TrCH`Required

Structure, structure array

Transport channels in the CCTrCH, specified as a structure or a structure array.

`TrCH.Name`Required

Character vector or 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 ms, 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.

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 physical channel data block with random seed = 511.

• ...`CCTrCH.TrCh(1).DataSource = {'PN9',5}`, generates a physical 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)`].

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.

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`.

#### DPCCH Substructure

Include the `DPCCH` substructure in the `config` structure to add the dedicated physical control channel to the output structure. The `DPCCH` 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

DPCCH slot format number, specified as 0, 1, 2, 3, 4, or 5.

`Power`Required

Float, –`inf`, `inf`

DPCCH 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, specified as a nonnegative integer in the interval [0, 1023].

`FBIData`Required

Binary scalar, binary vector

Feedback information data, specified as a binary scalar or a vector with binary entries.

#### HSUPA Substructure

Include the `HSUPA` substructure in the `config` structure to add the high speed uplink packet access information and channels to the output structure. The `HSUPA` 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.

`CodeCombination`Required

Positive integer, vector

Valid one-code combinations for BPSK modulation are: 2, 4, 8, 16, 32, 64, 128, and 256.

Valid two-code combinations for BPSK modulation are [2 2] and [4 4].

The valid four-code combination for BPSK and 4PAM modulation is [2 2 4 4].

`EDPDCHPower`Required

Float, –`inf`, `inf`

E-DPDCH channel power in dB, specified as a float, –`inf`, or `inf`.

`EDPCCHPower`RequiredFloat, –`inf`, `inf`

E-DPCCH channel power in dB, specified as a float, –`inf`, or `inf`.

`RSNSequence`Required

Vector

Retransmission sequence numbers, specified as a vector whose entries are 0, 1, 2, or 3. The length of this vector determines the number of retransmissions.

`ETFCI`Required

Nonnegative integer

E-TFCI value, specified as a nonnegative integer in the interval [0, 127].

`HappyBit`Required

0 or 1

Happy bit, specified as 0 or 1.

`DataSource`Required

Scalar, vector, character vector, cell array, or string scalar

E-DPDCH data source, specified as a binary scalar, a vector with binary entries, a character vector, a cell array, or a string scalar.

When specifying `DataSrouce` 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 `'EDCH'`.

`EDCH`Required

Structure

Enhanced dedicated channel (EDCH), specified as a structure.

`EDCH.BlockSize`Required

Nonnegative integer

Transport block size, specified as a nonnegative integer.

`EDCH.TTI`Required

2, 10

Transmission Time Interval (TTI), in ms, specified as 2 or 10.

`EDCH.Modulation`Required`'BPSK'`, `'4PAM'`

Modulation scheme, specified as `'BPSK'` or `'4PAM'`.

`EDCH.DataSource`Required

Scalar, vector, character vector, cell array, or string scalar

E-DCH transport 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.

#### HSDPCCH Substructure

Include `HSDPCCH` substructure in `config` structure to add the high speed dedicated physical control channel to the output structure. The `HSDPCCH` 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`

HS-DPCCH channel power in dB, specified as a float, –`inf`, or `inf`.

`CQI`Required

Nonnegative integer, vector

CQI values, specified as a nonnegative integer or a vector whose entries are nonnegative integers in the interval [0, 30].

`HARQACK`Required

Nonnegative integer, vector

HARQACK messages, specified as a nonnegative integer or a vector whose entries are nonnegative integers in the interval [0, 3].

`UEMIMO`Required

0, 1

Flag to indicate MIMO mode, specified as 0 or 1.

## 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.

## Version History

Introduced in R2015a