 shown in Figure 10-30, with network slicing, operators can deploy applications at different locations depending on their latency, jitter, and synchronization requirements and adopt the necessary RAN split to support the bandwidth. VOICE Radio access IOT apps Telco apps URLLC Service platform Cloud SP Core SP edge Access Connected device Figure 10-30 Network Slicing Network slices can be a dedicated resource or a shared resource or can even span across multiple parts of the network or across multiple operators. The idea is that the operators will deploy a slice type that satisfies the requirements of multiple traffic flows that align to the same characteristics. A good way to think about network slicing is that it is a form of QoS that ensures that the required conditions and resources are available and are guaranteed end-to-end for the use of any application that needs to use it. The full timing support profile, G.8275.1, is recommended with network slicing to avoid complexity and maintain accurate timing across all categories of services. However, vari- ous deployment use cases are evolving with 5G slicing and are currently still open for further study. 10.5 5G New Radio Synchronization Requirements The preceding sections discussed synchronization use cases and the requirements for 4G LTE and LTE-A, and 5G NR adopts many of the same use cases. But 5G uses more flexible spectrum and deploys it across a wider range of heterogenous cell sites. In addition to the basic needs of LTE, 5G also adds deployment scenarios and radio techniques that demand stringent synchronization. For LTE, the TS 36.104 and TS 36.133 3GPP technical standards represent the key documents that describe base station transmission and reception requirements. For 5G, the equivalent documents are TS 38.104 and TS 38.133. For numerous use cases, these documents define requirements for the maximum TAE that is allowed at the air interface. The RAN standards development organizations, such as eCPRI, IEEE 802.1CM, and O-RAN, re- flect these requireme