defined in 802.1CM, based on (and aligned to) base station requirements as defined in 3GPP. Bridging functions The 802.1CM standard defines bridging functions that are important to the fronthaul bridged network. Note that these may not apply to the REC/RE nodes. Latency components input queueing delay (likely not present) interference delay between time that a frame was selected for transmission and actual transmission-caused by queued-up frame of higher or same priority as the chosen frame frame transmission delay (time to transmit one frame at the transmission rate of the port) LAN propagation delay-physical delay due to LAN link length store-and-forward delay associated with the bridge function Frame preemption which is the suspension of the transmission of a "current" frame by a higher priority frame. This feature is optionally supported by fronthaul bridges. Its value diminishes as port speeds increase. Network synchronization (PTP, SynchE, GPS, proprietary as described earlier). Flow control. Flow control support can invalidate latency guarantees and may have to be disabled on fronthaul bridges. Energy-efficient Ethernet. Like flow control, Energy-efficient Ethernet may be prohibitive to fronthaul bridges and needs to be disabled. Fronthaul profiles The 802.1CM standard defines two feature profiles for fronthaul that both apply to Class 1 and Class 2 traffic (note, Class 1 and Class 2 traffic requirements are common). The profiles define three types of fronthaul traffic: high-priority fronthaul (HPF) with end-to-end latency (100 us associated with Class 1 and 2 fast user plane (IQ) medium-priority fronthaul (MPF) with end-to-end latency <1 ms associated with Class 2 slow user plane and Class 2 fast C&M low-priority fronthaul (LPF) with end-to-end latency < 100 ms associated with C&M Profile A shall be supported by the bridges in a fronthaul network: It supports maximum frame size of up to 2000 B, with actual applied frame size potentially smaller (e.g., 802.1Q frames of 1522 B). It has three traffic priorit