292 .. _fig-epc-data-flow-dl: |
292 .. _fig-epc-data-flow-dl: |
293 |
293 |
294 .. figure:: figures/epc-data-flow-dl.* |
294 .. figure:: figures/epc-data-flow-dl.* |
295 :align: center |
295 :align: center |
296 |
296 |
297 Data flow in the dowlink between the internet and the UE |
297 Data flow in the downlink between the internet and the UE |
298 |
298 |
299 To begin with, we consider the case of the downlink, which is depicted |
299 To begin with, we consider the case of the downlink, which is depicted |
300 in Figure :ref:`fig-epc-data-flow-dl`. |
300 in Figure :ref:`fig-epc-data-flow-dl`. |
301 Downlink Ipv4 packets are generated from a generic remote host, and |
301 Downlink Ipv4 packets are generated from a generic remote host, and |
302 addressed to one of the UE device. Internet routing will take care of |
302 addressed to one of the UE device. Internet routing will take care of |
530 Transmission Bandwidth Configuration in use. |
530 Transmission Bandwidth Configuration in use. |
531 |
531 |
532 For certain bandwidth |
532 For certain bandwidth |
533 values not all the RBs are usable, since the |
533 values not all the RBs are usable, since the |
534 group size is not a common divisor of the group. This is for instance the case |
534 group size is not a common divisor of the group. This is for instance the case |
535 when the bandwith is equal to 25 RBs, which results in a RBG size of 2 RBs, and |
535 when the bandwidth is equal to 25 RBs, which results in a RBG size of 2 RBs, and |
536 therefore 1 RB will result not addressable. |
536 therefore 1 RB will result not addressable. |
537 In uplink the format of the DCIs is different, since only adjacent RBs |
537 In uplink the format of the DCIs is different, since only adjacent RBs |
538 can be used because of the SC-FDMA modulation. As a consequence, all |
538 can be used because of the SC-FDMA modulation. As a consequence, all |
539 RBs can be allocated by the eNB regardless of the bandwidth |
539 RBs can be allocated by the eNB regardless of the bandwidth |
540 configuration. |
540 configuration. |
1091 -------- |
1091 -------- |
1092 |
1092 |
1093 The physical layer model provided in this LTE simulator is based on |
1093 The physical layer model provided in this LTE simulator is based on |
1094 the one described in [Piro2011]_, with the following modifications. The model now includes the |
1094 the one described in [Piro2011]_, with the following modifications. The model now includes the |
1095 inter cell intereference calculation and the simulation of uplink traffic, including both packet transmission and CQI generation. |
1095 inter cell intereference calculation and the simulation of uplink traffic, including both packet transmission and CQI generation. |
|
1096 |
|
1097 .. only:: latex |
|
1098 |
|
1099 .. raw:: latex |
|
1100 |
|
1101 \clearpage |
|
1102 |
|
1103 Subframe Structure |
|
1104 ^^^^^^^^^^^^^^^^^^ |
|
1105 |
|
1106 The subframe is divided into control and data part as described in Figure :ref:`fig-lte-subframe-structure`. |
|
1107 |
|
1108 .. _fig-lte-subframe-structure: |
|
1109 |
|
1110 .. figure:: figures/lte-subframe-structure.* |
|
1111 :width: 50px |
|
1112 |
|
1113 Lte subframe division. |
|
1114 |
|
1115 |
|
1116 Considering the granularity of the simulator based on RB, the control and the reference signaling have to be consequently modeled considering this constraint. According to the standard [TS36.211]_, the downlink control frame starts at the beginning of each subframe and lasts up to three symbols across the whole system bandwidth, where the actual duration is provided by the Physical Control Format Indicator Channel (PCFICH). The information on the allocation are then mapped in the remaining resource up to the duration defined by the PCFICH, in the so called Physical Downlink Control Channel (PDCCH). A PDCCH transports a single message called Downlink Control Information (DCI) coming from the MAC layer, where the scheduler indicates the resource allocation for a specific user. |
|
1117 The PCFICH and PDCCH are modeled with the transmission of the control frame of a fixed duration of 3/14 of milliseconds spanning in the whole available bandwidth, since the scheduler does not estimate the size of the control region. This implies that a single transmission block models the entire control frame with a fixed power (i.e., the one used for the PDSCH) across all the available RBs. According to this feature, this transmission represents also a valuable support for the Reference Signal (RS). This allows of having every TTI an evaluation of the interference scenario since all the eNB are transmitting (simultaneously) the control frame over the respective available bandwidths. We note that, the model does not include the power boosting since it does not reflect any improvement in the implemented model of the channel estimation. |
|
1118 |
|
1119 |
|
1120 The Sounding Reference Signal (SRS) is modeled similar to the downlink control frame. The SRS is periodically placed in the last symbol of the subframe in the whole system bandwidth. The RRC module already includes an algorithm for dynamically assigning the periodicity as function of the actual number of UEs attached to a eNB according to the UE-specific procedure (see Section 8.2 of [TS36.213]_). |
|
1121 |
|
1122 |
|
1123 .. only:: latex |
|
1124 |
|
1125 .. raw:: latex |
|
1126 |
|
1127 \clearpage |
|
1128 |
|
1129 |
|
1130 |
1096 |
1131 |
1097 |
1132 |
1098 MAC to Channel delay |
1133 MAC to Channel delay |
1099 ^^^^^^^^^^^^^^^^^^^^ |
1134 ^^^^^^^^^^^^^^^^^^^^ |
1100 |
1135 |
1146 example the spectrum licensing policies that are |
1181 example the spectrum licensing policies that are |
1147 discussed in [Ofcom2.6GHz]_. |
1182 discussed in [Ofcom2.6GHz]_. |
1148 |
1183 |
1149 |
1184 |
1150 |
1185 |
1151 PHY Error Model |
1186 Data PHY Error Model |
1152 --------------- |
1187 -------------------- |
1153 |
1188 |
1154 The simulator includes an error model of the data plane (i.e., PDSCH) according to the standard link-to-system mapping (LSM) techniques. The choice is aligned with the standard system simulation methodology of OFDMA radio transmission technology. Thanks to LSM we are able to maintain a good level of accuracy and at the same time limiting the computational complexity increase. It is based on the mapping of single link layer performance obtained by means of link level simulators to system (in our case network) simulators. In particular link the layer simulator is used for generating the performance of a single link from a PHY layer perspective, usually in terms of code block error rate (BLER), under specific static conditions. LSM allows the usage of these parameters in more complex scenarios, typical of system/network simulators, where we have more links, interference and "colored" channel propagation phenomena (e.g., frequency selective fading). |
1189 The simulator includes an error model of the data plane (i.e., PDSCH and PUSCH) according to the standard link-to-system mapping (LSM) techniques. The choice is aligned with the standard system simulation methodology of OFDMA radio transmission technology. Thanks to LSM we are able to maintain a good level of accuracy and at the same time limiting the computational complexity increase. It is based on the mapping of single link layer performance obtained by means of link level simulators to system (in our case network) simulators. In particular link the layer simulator is used for generating the performance of a single link from a PHY layer perspective, usually in terms of code block error rate (BLER), under specific static conditions. LSM allows the usage of these parameters in more complex scenarios, typical of system/network simulators, where we have more links, interference and "colored" channel propagation phenomena (e.g., frequency selective fading). |
1155 |
1190 |
1156 To do this the Vienna LTE Simulator [Vienna]_ has been used for what concerns the extraction of link layer performance and the Mutual Information Based Effective SINR (MIESM) as LSM mapping function using part of the work recently published by the Signet Group of University of Padua [PaduaPEM]_. |
1191 To do this the Vienna LTE Simulator [Vienna]_ has been used for what concerns the extraction of link layer performance and the Mutual Information Based Effective SINR (MIESM) as LSM mapping function using part of the work recently published by the Signet Group of University of Padua [PaduaPEM]_. |
1157 |
1192 |
1158 |
1193 |
1159 MIESM |
1194 MIESM |
1286 |
1321 |
1287 The model implemented uses the curves for the LSM of the recently LTE PHY Error Model released in the ns3 community by the Signet Group [PaduaPEM]_ and the new ones generated for different CB sizes. The ``LteSpectrumPhy`` class is in charge of evaluating the TB BLER thanks to the methods provided by the ``LteMiErrorModel`` class, which is in charge of evaluating the TB BLER according to the vector of the perceived SINR per RB, the MCS and the size in order to proper model the segmentation of the TB in CBs. In order to obtain the vector of the perceived SINR two instances of ``LtePemSinrChunkProcessor`` (child of ``LteSinrChunkProcessor`` dedicated to evaluate the SINR for obtaining physical error performance) have been attached to UE downlink and eNB uplink ``LteSpectrumPhy`` modules for evaluating the error model distribution respectively of PDSCH (UE side) and ULSCH (eNB side). |
1322 The model implemented uses the curves for the LSM of the recently LTE PHY Error Model released in the ns3 community by the Signet Group [PaduaPEM]_ and the new ones generated for different CB sizes. The ``LteSpectrumPhy`` class is in charge of evaluating the TB BLER thanks to the methods provided by the ``LteMiErrorModel`` class, which is in charge of evaluating the TB BLER according to the vector of the perceived SINR per RB, the MCS and the size in order to proper model the segmentation of the TB in CBs. In order to obtain the vector of the perceived SINR two instances of ``LtePemSinrChunkProcessor`` (child of ``LteSinrChunkProcessor`` dedicated to evaluate the SINR for obtaining physical error performance) have been attached to UE downlink and eNB uplink ``LteSpectrumPhy`` modules for evaluating the error model distribution respectively of PDSCH (UE side) and ULSCH (eNB side). |
1288 |
1323 |
1289 The model can be disabled for working with a zero-losses channel by setting the ``PemEnabled`` attribute of the ``LteSpectrumPhy`` class (by default is active). This can be done according to the standard ns3 attribute system procedure, that is:: |
1324 The model can be disabled for working with a zero-losses channel by setting the ``PemEnabled`` attribute of the ``LteSpectrumPhy`` class (by default is active). This can be done according to the standard ns3 attribute system procedure, that is:: |
1290 |
1325 |
1291 Config::SetDefault ("ns3::LteSpectrumPhy::PemEnabled", BooleanValue (false)); |
1326 Config::SetDefault ("ns3::LteSpectrumPhy::DataErrorModelEnabled", BooleanValue (false)); |
1292 |
1327 |
|
1328 Control Channels PHY Error Model |
|
1329 -------------------------------- |
|
1330 |
|
1331 The simulator includes the error model for downlink control channels (PCFICH and PDCCH), while in uplink it is assumed and ideal error-free channel. The model is based on the MIESM approach presented before for considering the effects of the frequency selective channel since most of the control channels span the whole available bandwidth. |
|
1332 |
|
1333 |
|
1334 PCFICH + PDCCH Error Model |
|
1335 ^^^^^^^^^^^^^^^^^^^^^^^^^^ |
|
1336 |
|
1337 The model adopted for the error distribution of these channels is based on an evaluation study carried out in the RAN4 of 3GPP, where different vendors investigated the demodulation performance of the PCFICH jointly with PDCCH. This is due to the fact that the PCFICH is the channel in charge of communicating to the UEs the actual dimension of the PDCCH (which spans between 1 and 3 symbols); therefore the correct decodification of the DCIs depends on the correct interpretation of both ones. In 3GPP this problem have been evaluated for improving the cell-edge performance _[FujitsuWhitePaper], where the interference among neighboring cells can be relatively high due to signal degradation. A similar problem has been notices in femto-cell scenario and, more in general, in HetNet scenarios the bottleneck has been detected mainly as the PCFICH channel _[Bharucha2011], where in case of many eNBs are deployed in the same service area, this channel may collide in frequency, making impossible the correct detection of the PDCCH channel, too. |
|
1338 |
|
1339 In the simulator, the SINR perceived during the reception has been estimated according to the MIESM model presented above in order to evaluate the error distribution of PCFICH and PDCCH. In detail, the SINR samples of all the RBs are included in the evaluation of the MI associated to the control frame and, according to this values, the effective SINR (eSINR) is obtained by inverting the MI evaluation process. It has to be noted that, in case of MIMO transmission, both PCFICH and the PDCCH use always the transmit diversity mode as defined by the standard. According to the eSINR perceived the decodification error probability can be estimated as function of the results presented in _[R4-081920]. In case an error occur, the DCIs discarded and therefore the UE will be not able to receive the correspondent Tbs, therefore resulting lost. |
1293 |
1340 |
1294 |
1341 |
1295 MIMO Model |
1342 MIMO Model |
1296 ---------- |
1343 ---------- |
1297 |
1344 |
1305 * MIMO-OSIC-MMSE: :math:`\mu = 12.6` and :math:`\sigma = 15.5` [dB]. |
1352 * MIMO-OSIC-MMSE: :math:`\mu = 12.6` and :math:`\sigma = 15.5` [dB]. |
1306 * MIMO-ZF: :math:`\mu = 10.3` and :math:`\sigma = 12.6` [dB]. |
1353 * MIMO-ZF: :math:`\mu = 10.3` and :math:`\sigma = 12.6` [dB]. |
1307 |
1354 |
1308 |
1355 |
1309 Therefore the PHY layer implements the MIMO model as the gain perceived by the receiver when using a MIMO scheme respect to the one obtained using SISO one. We note that, these gains referred to a case where there is no correlation between the antennas in MIMO scheme; therefore do not model degradation due to paths correlation. |
1356 Therefore the PHY layer implements the MIMO model as the gain perceived by the receiver when using a MIMO scheme respect to the one obtained using SISO one. We note that, these gains referred to a case where there is no correlation between the antennas in MIMO scheme; therefore do not model degradation due to paths correlation. |
1310 |
|
1311 .. only:: latex |
|
1312 |
|
1313 .. raw:: latex |
|
1314 |
|
1315 \clearpage |
|
1316 |
|
1317 Reference and Control Signaling |
|
1318 ------------------------------- |
|
1319 |
|
1320 Considering the granularity of the simulator based on RB, the control and the reference signaling have to be consequently modeled considering this constraint. On this matter, the simulator splits the transmission of the data frame respect to the control one. According to the standard [TS36.211]_, the control frame starts at the beginning of each subframe and lasts up to three symbols. The actual duration is provided by the Physical Control Format Indicator Channel (PCFICH) by means of three different codewords of 32 bits in order to make it enough robust. These 32 bits are mapped to 16 resource elements (RE), a subcarrier per 1 symbol, using QPSK modulation. The information on the allocation are then mapped in the remaining resource up to the duration defined by the PCFICH, in the so called Physical Downlink Control Channel (PDCCH). A PDCCH transports a single message called Downlink Control Information (DCI) coming from the MAC layer, where the scheduler indicates the resource allocation for a specific user. Each PDCCH is transmitted in a Control Channel Element (CCE), which is defined as group of nine sets of four REs. |
|
1321 According to the channel conditions the CCEs allocated can be 1, 2, 4 or 8, which correspond respectively to PDCCH format 0, 1, 2 and 3. Each PDCCH carries one of the possible 10 DCI formats configurations, modeling uplink and downlink assignment messages. |
|
1322 |
|
1323 |
|
1324 |
|
1325 PCFICH & PDDCH |
|
1326 ^^^^^^^^^^^^^^ |
|
1327 |
|
1328 The PDCCH is modeled with the transmission of the control frame of a fixed duration of 3/14 of milliseconds spanning in the whole available bandwidth. This implies that a single block transmission models the entire control frame with a fixed power (i.e., the one used for the PDSCH) across all the available RBs. The SINR perceived during the reception of this channel has been estimated according to the MIESM model presented above in order to evaluate the error distribution of PCFICH and PDCCH. In detail, the SINR samples of all the RBs are included in the evaluation of the MI associated to the control frame and, according to this values, the effective SINR is obtained by inverting the MI evaluation process. |
|
1329 |
|
1330 The PCFICH error distribution is modeled considering the link level simulation curves of the performance of the PCFICH in AWGN channel presented in [Milos2012]_, by means of look-up tables according to the transmission mode used (e.g., SISO or MIMO) and the SINR evaluated as described before. |
|
1331 |
|
1332 While for what concern the PDCCH, the correct reception of all the PDCCHs is modeled with a configurable power threshold on the perceived SINR, where the default value is taken from Section 10.3.3 of [Sesia2009]_ where the performance of the convolutional turbo codes of PDCCH (i.e., with state tailbiting) are presented. This implies that all the DCIs can be correctly decoded only in case of the perceived SINR is above the threshold. In doing this, we are assuming that the DCIs are randomly placed in the control frame and therefore always interfere with the ones of other BSs. According to [Sesia2009]_, the number of bits of the DCIs are at most of 62 bits. Therefore, the default value is taken for a given PDCCH fixed dimension of 62 bits and a considering a rate of :math:`1/3`, which corresponds to 2.4 dB. According to this model, the control frame does not have any limitation in the PDCCHs that can be transmitted. Finally, It has to be noted that, in case of MIMO transmission, the PDCCH uses always the transmit diversity mode according to the standard. |
|
1333 |
|
1334 |
|
1335 Reference Signal |
|
1336 ^^^^^^^^^^^^^^^^ |
|
1337 |
|
1338 The Reference Signal (RS) is modeled according to the SINR perceived during the reception of the control frame. This allows of having every TTI an evaluation of the interference scenario since all the eNB are transmitting (simultaneously) the control frame over the respective available bandwidths. We note that, the model does not include the power boosting since it does not reflect any improvement in the implemented model of the channel estimation. |
|
1339 |
|
1340 |
|
1341 PUCCH |
|
1342 ^^^^^ |
|
1343 |
|
1344 The PUCCH is modeled with an error free channel. |
|
1345 |
|
1346 |
|
1347 Sounding Reference Signal (SRS) |
|
1348 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
|
1349 |
|
1350 The SRS is modeled similar to the downlink control frame. The SRS is periodically placed in the last symbol of the subframe; therefore when a SRS signal has to be sent, the data frame will last on the 13th symbol in order to leave space for the SRS, which will be sent in the whole system bandwidth. The SINR can be evaluated according to MIESM model as done for RS. For what concern the periodicity, it can be defined as an integer multiple of TTIs; however we remark that the standard allows the following values: 2, 5, 10, 20, 40, 80, 160 or 320 TTIs. |
|
1351 |
|
1352 |
|
1353 .. only:: latex |
|
1354 |
|
1355 .. raw:: latex |
|
1356 |
|
1357 \clearpage |
|
1358 |
1357 |
1359 |
1358 |
1360 ----------------------- |
1359 ----------------------- |
1361 Channel and Propagation |
1360 Channel and Propagation |
1362 ----------------------- |
1361 ----------------------- |