 triggers the last message in the RACH procedure (message Chapter 2 System components, requirements, and interfaces 91 Slot (14 symbols) CORESET (per subcarrier spacing) Type0-PDCCH search space SS/PBCH block and coreset MUX pattern Number of RBs N CORESET Number of symbols N CORESET Offset (RBs) CORESET (per frequency range and mux pattern) Type0-PDCCH search space monitoring params CORESET Number of search space/slot First symbol index Multiplexing pattern 1 (<6GHz), PDCCH monitoring for 2 slots starting no no = (O . 2 + rounddown(i- M))mod slot SFN mod2 = 0 if rounddown(0 2'+rounddown( M)/N frame, slot )mod2 = 0 SFN mod2 = 1 ifrounddown(O.2"+rounddown(i M)/N frame, slot)mod2 = 1 u is subcarrier spacing for PDCCH resources in control resource set Multiplexing pattern 2&3, PDCCH monitoring for 1 slot FIGURE 2-43 PDCCH Control Resource Set. 4, from base station to client) which is the contention resolution message that should contain the same contention resolution identifier that the client transmitted to the base station in message 3. 802.1CM The 802.1CM (Time-Sensitive Networking for Fronthaul) standard defines Ethernet profiles necessary to build networks capable of transporting fronthaul streams. Fronthaul streams are defined as flows between a base station and a radio head. 802.1CM profiles include definition of: MAC Service Specifications (802.1AC) MAC/PHY Specifications Express Traffic Interspersing Frame Preemption Time Synchronization and PTP (IEEE1588) Telecom Profile Specification (IEEE1588) Synchronous Ethernet Specification 92 Open Radio Access Network (O-RAN) Systems Architecture and Design Note that the 802.1CM standard defines the complete fronthaul, and not only RE (aka Radio Head/RRH/RU) or RE Controller/REC (aka eNB/gNB/Base Station/DU) equipment. Specifically, this includes definition of Ethernet bridge and forwarding requirements. Note that RE/REC terminology is leveraged from CPRI standards. Traffic classes 802.1CM defines two classes (types) of fronthaul traffic, both over Ethernet: Class 1