not geographically co-located, this class of service may be routable to multiple destinations. Upon addition, deletion, or modification of the slicing operations, the slicing-agnostic transport is not expected to adapt to the change and to perform any reconfiguration process for optimization of the transport network. In slicing-aware transport mode, while the user plane remains class of service based and the transport QoS is maintained at class of service level, a slicing-aware transport network interfaces with the network slicing orchestrator which is aware of the network slicing operation. Thus, the transport operation can be controlled and managed via the NGFI OAM configuration and provisioning functions for the purpose of network slicing optimi- zation. As depicted in Fig. 1.38, the slice-to-class of service mapping is required to sup- port class of service-based transport operation and is realized within the transport network and controlled by OAM configuration function that communicates with the network slic- ing orchestrator. This slice-to-class of service mapping correspondence is flexible by nature and should be dynamically or semi-dynamically reconfigured without service inter- ruption. Furthermore, the transport OAM monitoring function reports the transport KPIs to the network slicing orchestrator, providing a means of feedback for integrated network optimization. Upon deletion, addition, or any modification of the network slicing services, the slice-aware transport adapts to the changes and performs seamless reconfiguration over the transport network for the purpose of overall network optimization. A slice-based transport that is fully optimized for network slicing should not be class of service-based where each slice traffic should be individually identified, labeled, and transported accord- ing to its own QoS requirements [78]. 1.1.6.3 Backhaul Transport Options The increasing demand for broadband wireless applications has a significant effect on the entire mobile infrastructure including the mobile