Skip to main content

Cell

Description

Cell structure defines an EUTRA or NR cell, with all of its parameters.


Band field of tag band

Band to be used to configure AN and its radio devices. It supports both LTE notation and NR notation. To use LTE bands, prepend the band with "b" and to use NR bands, prepend the band with "n". Trirematics supports both FR1 and FR2, however whether AN is able to operate with FR2 depends on the vendor. The Band also determines the duplex mode and valid Bandwidth values as given by standard. The configurations not respecting the 3GPP standard should be rejected. For a complete list of supported bands, see the following links: LTE: https://en.wikipedia.org/wiki/LTE_frequency_bands NR: https://en.wikipedia.org/wiki/5G_NR_frequency_bands

Kind: Band
Tag: band
Manager Tag: band
Data Type: Alias
Optional: False


Bandwidth field of tag bandwidth

Bandwidth of the used channel in MHz, yet for clarity "MHz" should be appended for each value. Having the Bandwidth and SubcarrierSpacing defined, the Number of Resource Blocks (NRBs) is computed internally, based on FR1 or FR2.

Kind: string
Tag: bandwidth
Manager Tag: bandwidth
Data Type: string
Enumeration: "1.4MHz", "3MHz", "5MHz", "10MHz", "15MHz", "20MHz", "25MHz", "30MHz", "35MHz", "40MHz", "45MHz", "50MHz", "60MHz", "70MHz", "80MHz", "90MHz", "100MHz", "200MHz", "400MHz", "800MHz", "1600MHz", "2000MHz"
Optional: False


ARFCN field of tag arfcn

Absolute Radio-Frequency Channel Number (ARFCN) uniquely defines the UL and DL frequencies that AN operates on. The values should be compatible with 3GPP standard. Depending on the Stack, either EARFCN or NR-ARFCN should be used. The values are most likely fed to the workload as it is, but they might be translated to frequency values in the configurator plugins.

Kind: int32
Tag: arfcn
Manager Tag: arfcn
Data Type: int32
Maximum Value: 3279167
Minimum Value: 0
Optional: False


Offset field of tag offset

Offset is used to optionally shift the start of the band to a different frequency. The values are defined in MHz, but for clarify the term "MHz" should be appended. No checks are done for the offset, so please use with caution.

Kind: *string
Tag: offset
Manager Tag: offset
Data Type: Pointer
Optional: True
Regular Expression: \d+MHz


SubcarrierSpacing field of tag subcarrier-spacing

SubcarrierSpacing is to define SCS and numerology. The values are defined in kHz, but for clarity the term "kHz" should be appended. For different Stack and Band values, the user should only use the standard values. To remain compatible with 4G LTE, this parameter is kept optional with 15kHz as default.

Kind: *string
Tag: subcarrier-spacing
Manager Tag: subcarrier-spacing
Data Type: Pointer
Enumeration: "15kHz", "30kHz", "60kHz", "120kHz", "240kHz", "480kHz", "960kHz"
Optional: True


Filters field of tag filters

Filters are used for slice association, likewise the filters that are used for the access network. The filters are applied after the access network filters.

Kind: *./api/v1.SliceFilters
Tag: filters
Manager Tag: -
Data Type: Pointer
Optional: True


Groups field of tag groups

Groups are optionally used to define the associations of the cells inter-RAN and intra-RAN. Four types of groups are supported, for four use cases: 1. Carrier Component Group (CCG), useful for carrier aggregation. 2. Non-StandAlone group (NSA), useful for NSA deployments. 3. HandOver Group (HOG), useful for handover deployments. 4. Dynamic Spectrum Sharing Group (DSS), useful for dynamic spectrum sharing between LTE and NR.

Tag: groups
Manager Tag: groups
Data Type: Slice
Optional: True


TDDConfig field of tag tdd-config

TDDConfig is used to define the TDD configuration of the cell. This configuration is only accepted if the Band is in the TDD duplex mode.

Kind: *./api/v1.TDDConfig
Tag: tdd-config
Manager Tag: tdd-config
Data Type: Pointer
Optional: True