101 E-UTRA Absolute Radio Frequency Channel Number (EARFCN) |
101 E-UTRA Absolute Radio Frequency Channel Number (EARFCN) |
102 ------------------------------------------------------- |
102 ------------------------------------------------------- |
103 |
103 |
104 The test suite ``lte-earfcn`` checks that the carrier frequency used |
104 The test suite ``lte-earfcn`` checks that the carrier frequency used |
105 by the LteSpectrumValueHelper class (which implements the LTE spectrum |
105 by the LteSpectrumValueHelper class (which implements the LTE spectrum |
106 model) is done in compliance with [TS36.101]_, where the E-UTRA |
106 model) is done in compliance with [TS36101]_, where the E-UTRA |
107 Absolute Radio Frequency Channel Number (EARFCN) is defined. The test |
107 Absolute Radio Frequency Channel Number (EARFCN) is defined. The test |
108 vector for this test suite comprises a set of EARFCN values and the |
108 vector for this test suite comprises a set of EARFCN values and the |
109 corresponding carrier frequency calculated by hand following the |
109 corresponding carrier frequency calculated by hand following the |
110 specification of [TS36.101]_. The test passes if the carrier frequency |
110 specification of [TS36101]_. The test passes if the carrier frequency |
111 returned by LteSpectrumValueHelper is the same as the known value for |
111 returned by LteSpectrumValueHelper is the same as the known value for |
112 each element in the test vector. |
112 each element in the test vector. |
113 |
113 |
114 |
114 |
115 |
115 |
205 checking that the obtained throughput performance is equal among users and |
205 checking that the obtained throughput performance is equal among users and |
206 matches a reference throughput value obtained according to the SINR perceived |
206 matches a reference throughput value obtained according to the SINR perceived |
207 within a given tolerance. |
207 within a given tolerance. |
208 |
208 |
209 The test vector is obtained according to the values of transport block |
209 The test vector is obtained according to the values of transport block |
210 size reported in table 7.1.7.2.1-1 of [TS36.213]_, considering an |
210 size reported in table 7.1.7.2.1-1 of [TS36213]_, considering an |
211 equal distribution of the physical resource block among the users |
211 equal distribution of the physical resource block among the users |
212 using Resource Allocation Type 0 as defined in Section 7.1.6.1 of |
212 using Resource Allocation Type 0 as defined in Section 7.1.6.1 of |
213 [TS36.213]_. Let :math:`\tau` be the TTI duration, :math:`N` be the |
213 [TS36213]_. Let :math:`\tau` be the TTI duration, :math:`N` be the |
214 number of UEs, :math:`B` the transmission bandwidth configuration in |
214 number of UEs, :math:`B` the transmission bandwidth configuration in |
215 number of RBs, :math:`G` the RBG size, :math:`M` the modulation and |
215 number of RBs, :math:`G` the RBG size, :math:`M` the modulation and |
216 coding scheme in use at the given SINR and :math:`S(M, B)` be the |
216 coding scheme in use at the given SINR and :math:`S(M, B)` be the |
217 transport block size in bits as defined by 3GPP TS 36.213. We first |
217 transport block size in bits as defined by 3GPP TS 36.213. We first |
218 calculate the number :math:`L` of RBGs allocated to each user as |
218 calculate the number :math:`L` of RBGs allocated to each user as |
271 throughput value by dividing the throughput achievable by a single UE |
271 throughput value by dividing the throughput achievable by a single UE |
272 at the given SNR by the total number of UEs. |
272 at the given SNR by the total number of UEs. |
273 Let :math:`\tau` be the TTI duration, :math:`B` the transmission |
273 Let :math:`\tau` be the TTI duration, :math:`B` the transmission |
274 bandwidth configuration in number of RBs, :math:`M` the modulation and |
274 bandwidth configuration in number of RBs, :math:`M` the modulation and |
275 coding scheme in use at the given SINR and :math:`S(M, B)` be the |
275 coding scheme in use at the given SINR and :math:`S(M, B)` be the |
276 transport block size as defined in [TS36.213]_. The reference |
276 transport block size as defined in [TS36213]_. The reference |
277 throughput :math:`T` in bit/s achieved by each UE is calculated as |
277 throughput :math:`T` in bit/s achieved by each UE is calculated as |
278 |
278 |
279 .. math:: |
279 .. math:: |
280 |
280 |
281 T = \frac{S(M,B)}{\tau N} |
281 T = \frac{S(M,B)}{\tau N} |
408 |
408 |
409 MIMO Model |
409 MIMO Model |
410 ---------- |
410 ---------- |
411 |
411 |
412 The test suite ``lte-mimo`` aims at verifying both the effect of the gain considered for each Transmission Mode on the system performance and the Transmission Mode switching through the scheduler interface. The test consists on checking whether the amount of bytes received during a certain window of time (0.1 seconds in our case) corresponds to the expected ones according to the values of transport block |
412 The test suite ``lte-mimo`` aims at verifying both the effect of the gain considered for each Transmission Mode on the system performance and the Transmission Mode switching through the scheduler interface. The test consists on checking whether the amount of bytes received during a certain window of time (0.1 seconds in our case) corresponds to the expected ones according to the values of transport block |
413 size reported in table 7.1.7.2.1-1 of [TS36.213]_, similarly to what done for the tests of the schedulers. |
413 size reported in table 7.1.7.2.1-1 of [TS36213]_, similarly to what done for the tests of the schedulers. |
414 |
414 |
415 The test is performed both for Round Robin and Proportional Fair schedulers. The test passes if the measured throughput matches with the reference throughput within a relative tolerance of 0.1. This tolerance is needed to account for the |
415 The test is performed both for Round Robin and Proportional Fair schedulers. The test passes if the measured throughput matches with the reference throughput within a relative tolerance of 0.1. This tolerance is needed to account for the |
416 transient behavior at the beginning of the simulation and the transition phase between the Transmission Modes. |
416 transient behavior at the beginning of the simulation and the transition phase between the Transmission Modes. |
417 |
417 |
418 |
418 |