rchitecture and Design WG1: Overall use-cases and architecture Orchestration & Automation (eg ONAP): MANO, NMS RAN Intelligent Design Inventory Policy Configuration control (RIC) on-RT RAN Intelligent Controller (RIC) near-RT Applications Layer 3rd party Radio Connect Mobility Interference Trained Model Radio-Network Information Base E2: between near-RT and O-CU / O-DU Multi-RAT O-CU Protocol Stack CU-CP CU-CP PDCP-C PDCP-U F1: between NFVI Platforms: Virtualization Layer and COTS Platform near-RT and 0-CU/O-DU O-DU: RLC/MAC/PHY-high Open Fronthaul Interface O-RU: PHY-low/RF FIGURE 1-1 O-RAN Working Groups. O-RAN, Open Radio Access Networks. WG2 owns the definition of the non-Real-Time (RT) RAN Intelligent Controller (RIC) and the Al interface. The non-RT RIC controls radio resource management (RRM), higher layer procedure optimization, and RAN policy optimization, including Artificial Intelligence (AI)/ Machine Learning model application. Communication between the near-RT RIC and the non- RT RIC is defined by the Al interface-functionally, this interface carries policy-based guidance of near-RT RIC functions/use cases and appropriate feedback/input data in the return path. At its lowest level, non-RT RIC converts system goals (RAN intent) and observed parameters and counters to policies that guide the RT RIC toward fulfilling the system goals. Deliverables include: Al interface specification Working Group 3: Near-Real-time RIC and E2 Interface Workgroup WG3 owns the near-RT RIC architecture and functionalities. Deliverables include: Chapter 1 Open radio access network overview E2 interface specification. Note that the E2 interface is 3GPP-defined. WG3 provides a framework with a defined subset of 3GPP messages. Working Group 4: Open Fronthaul Interfaces Workgroup WG4 owns the definition of fronthaul interfaces. Deliverables include: Management plane (MP) specification. A NETCONF/YANG based M-Plane is used for supporting the management features including "start-up" installation, software management, configuration