tringent latency requirements have kept the fronthaul interface away from packet- switched schemes such as Ethernet. However, with the exponential increase in bandwidth requirements for 5G networks, packet-based transport schemes cannot be disregarded. The economy of scale and the statistical multiplexing gain of Ethernet are essential for the new fronthaul transport. In cooperation with CPRI Forum, IEEE 802.1 took the task of defining a new fronthaul transport standard under the IEEE 802.1cm38 38 project. The project was enti- tled, Time-Sensitive Networking (TSN)35 for fronthaul, which defines profiles for bridged Ethernet networks that will carry fronthaul payloads in response to requirements contributed by the CPRI forum. The requirements can be divided into three categories: 1. Class 1: I/Q and Control and Management (C&M) data 2. Synchronization 3. Class 2: eCPRI which has been recently added IEEE 802.1CM-time-sensitive networking for fronthaul (http://www.ieee802.org/1/pages/802.1cm.html) Time-sensitive networking is a standard developed by IEEE 802.1Q to provide deterministic messaging on standard Ethernet. Time-sensitive networking scheme is centrally managed with guaranteed delivery and minimized jitter using scheduling for those real-time applications that require deterministic behavior. Time- sensitive networking is a data link layer protocol and as such is part of the Ethernet standard. The forwarding decisions made by the time-sensitive networking bridges use the Ethernet header contents and not the Internet protocol address. The payloads of the Ethernet frames can be anything and are not limited to Internet protocol packets. This means that time-sensitive networking can be used in any environment and can carry the payload of any application. There are five main components in the time-sensitive networking solution as follows [78]: Time-sensitive networking flow: The time-critical communication between end devices where each flow has strict timing requirements and each time-sensitive networking flow 