STP.RSTP.Uplink Fast. Backbone Fast.

Explanation for Uplink Fast

http://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/10575-51.html
The goal of uplink fast is to immediately forwarding for the alternate port

Backbone Fast
http://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/12014-18.html
It speed up the STP converge while the indirect link failure to the root.

Both uplink fast and backbone fast is to speed up the STP recovery time.

For the RSTP, it has this two similar features built in.

https://supportforums.cisco.com/discussion/11152846/rapid-pvst-uplink-fast-backbone-fast

There seems to be an ongoing misunderstanding about the relation of BackboneFast and UplinkFast to RSTP.

The RSTP alone, by itself, has built-in mechanisms that provide a similar functionality to Cisco's proprietary BackboneFast and UplinkFast STP extensions. Therefore, activating the RSTP (or the RPVST/RPVST+) immediately gives you the advantages of BackboneFast and UplinkFast. However, the BackboneFast and UplinkFast themselves are distinct extensions and they are not activated along with RSTP. In fact, even if you configured them together with running RSTP, they would not be active because RSTP already provides their functionality, although by slightly different mechanisms. That fact is confirmed by your output of show span sum

To sum it up, the RSTP already incorporates the functionality of UplinkFast and BackboneFast (although not implemented exactly in the way the UplinkFast and BackboneFast implement it), and when you activate RSTP, you get UplinkFast-like and BackboneFast-like functionality. The UplinkFast and BackboneFast alone, however, are not and will not be activated.