october utc ok and after this here is now the detailled technical explanation and conclusive evidence for the ue categories and their achievable throughput the calculation of the theoretical dl throughput in mbit s according to the largest available carrier bandwidth of mhz is as follows a mhz carrier consists of ressource blocks rb each rb consists of subcarriers sc which can be divided into time slots ts each that carry odfm symbols each further we have a qam modulation scheme the maximum qam specified is qam which means there are bits symbol additionally we have x mimo antenna technology which allows two parallel data layers l in total this results in rb sc ts odfm symbols bit symbol l mbit s absolute theoretical technical maximum dl data rate per mhz carrier page now let's take a look at the ue categories this information derives from the specification document gpp ts page to let's take a look at table cat devices use coding scheme mcs for dl and mcs for ul this leads to tbs index for dl and for ul looking at table we now look at n prb of ressource blocks corresponds to mhz carrier for the tcs indices above we find and respectively this results in mbit s for the ul for the downlink we have x mimo so there are layers corresponding to table the available number of ressource blocks siso translates to for x mimo resulting in mbit s mbit s as can be seen this ist a bit less than the mbit s which are stated in the gpp ue table table in ts cat devices use coding scheme mcs for dl and ul so with the explanation above we find resulting in mbit s for ul again and with x mimo for dl mbit s or simply mbit s table in ts if we now reduce the carrier block size to mhz what happens the amount of ressource blocks reduces from to that's all the mcs coding scheme stays the same the conclusion is that a cat device is able to achieve a theoretical troughput of mbit s with mhz rb tables of spectrum subsequently a cat device in contrast can only reach mbit s according to these two tables and not around mbit s as previously discussed i hope this clarified the issue so far i doubt that the development group is wrong here in their own specification