A Discrete-Event Network Simulator
API
Loading...
Searching...
No Matches
ConfigToCheck Struct Reference

This test suite verifies following two things: More...

+ Collaboration diagram for ConfigToCheck:

Public Attributes

uint16_t m_dlBandwidth
 Downlink bandwidth.
 
uint32_t m_dlEarfcn
 Downlink EARFCN.
 
uint16_t m_ulBandwidth
 Uplink bandwidth.
 
uint32_t m_ulEarfcn
 Uplink EARFCN.
 

Detailed Description

This test suite verifies following two things:

  1. When CA is enabled and UE carriers configuration is different than the default one, we check that the UE is configured properly once it receives RRC Connection Reconfiguration message from eNB.
  2. A user can configure 2 or more eNBs and UEs with different configuration parameters, i.e, each eNB and UE can have different EARFCN and Bandwidths and a UE connects to an eNB with similar DL EARFCN. Here we check it with CA enabled but the end results will be the same if CA is not enabled and we have more than one eNBs and UEs with different configurations.

Since we do not need EPC to test the configuration, this test only simulates the LTE radio access with RLC SM.

Test 1 tests that the UE is configured properly after receiving RRC Connection Reconfiguration message from the eNB, which will overwrite UE default configuration done in LteHelper for the sake of creating PHY and MAC instances equal to the number of component carriers.

Test 2 tests that in a simulation scenario every eNB or UE can be configured with different EARFCNs and Bandwidths. This will check that the eNBs and UEs configuration is not static, as reported in BUG 2840. ConfigToCheck structure

Definition at line 53 of file lte-test-carrier-aggregation-configuration.cc.

Member Data Documentation

◆ m_dlBandwidth

◆ m_dlEarfcn

◆ m_ulBandwidth

◆ m_ulEarfcn


The documentation for this struct was generated from the following file: