|
|
| 1601 |
split the data uniformly between primary and secondary carrier. The test consists of checking that |
1601 |
split the data uniformly between primary and secondary carrier. The test consists of checking that |
| 1602 |
the throughput obtained over the different carriers are equal considering a given tolerance. For more |
1602 |
the throughput obtained over the different carriers are equal considering a given tolerance. For more |
| 1603 |
details about this test, see the section Carrier aggregation usage example. |
1603 |
details about this test, see the section Carrier aggregation usage example. |
|
|
1604 |
|
| 1605 |
|
| 1606 |
Carrier aggregation test for eNB and UE configuration |
| 1607 |
------------------------------------------------------ |
| 1608 |
|
| 1609 |
The test suite ``carrier-aggregation-config-test`` is a system test program, which verifies the following |
| 1610 |
two cases: |
| 1611 |
|
| 1612 |
* When carrier aggregation is enabled and UE carriers configuration is different than the default configuration |
| 1613 |
done in LteHelper, we check that the UE(s) is configured properly once it receives RRC Connection Reconfiguration |
| 1614 |
message from eNB. |
| 1615 |
|
| 1616 |
* A user can configure 2 or more eNBs and UEs with different configuration parameters, i.e, |
| 1617 |
each eNB and UE can have different EARFCN and Bandwidths and a UE connects to an eNB with similar DL EARFCN. |
| 1618 |
In this test, we check with CA enabled but the end results will be the same if carrier aggregation is not |
| 1619 |
enabled and we have more than one eNBs and UEs with different configurations. |
| 1620 |
|
| 1621 |
Since, we do not need EPC to test the configuration, this test only simulates the LTE radio access with RLC SM. |
| 1622 |
There are two test cases, Test 1 tests that the UE is configured properly after receiving RRC Connection Reconfiguration |
| 1623 |
message from the eNB, which will overwrite UE default configuration done in LteHelper for the sake of |
| 1624 |
creating PHY and MAC instances equal to the number of component carriers. Test 2, tests that every eNB or UE in a |
| 1625 |
simulation scenario can be configured with different EARFCNs and Bandwidths. For both the test cases, it also counts |
| 1626 |
the number of times the hooked trace source ``SCarrierConfigured`` get triggered. As, it reflects how many UEs |
| 1627 |
got attached to their respective eNB. If the count is not equal to the number of UEs in the scenario, the test will fail, |
| 1628 |
which could be the result of improper UE configuration. |
| 1629 |
|
| 1604 |
|
1630 |
|