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 MBits 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  ODFMSymbols each Further we have a QAM modulation scheme The maximum QAM specified is QAM which means there are  bitssymbol Additionally we have x MIMO antenna technology which allows two parallel data layers L In total this results in  RB   SC   TS   ODFMSymbols   bitSymbol   L   MBits Absolute theoretical technical maximum DL data rate per  MHz carrier  page  Now lets take a look at the UE categories This information derives from the specification document GPP TS   page  to  Lets 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 NPRB  of Ressource Blocks   corresponds to  MHz carrier For the TCS indices above we find  and  respectively This results in  MBits 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  MBits   MBits As can be seen this ist a bit less than the  MBits 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  MBits for UL again and with x MIMO for DL  MBits or simply  MBits Table  in TS  If we now reduce the carrier block size to  MHz  what happens The amount of ressource blocks reduces from  to   thats all The MCS coding scheme stays the same The conclusion is that a Cat device is able to achieve a theoretical troughput of  MBits with  MHz  RB Tables    of spectrum Subsequently a Cat device in contrast can only reach  MBits according to these two tables and not around  MBits as previously discussed I hope this clarified the issue so far I doubt that the development group is wrong here in their own specification