olicy, and configuration from the operators are pushed into the RAN configuration. The model also includes the RAN intelligent controller (RIC), 3 which can artificial intelligence (AI)/machine learning (ML) methods to optimize RAN performance. When finalized, the platform will feature a set of functions and interfaces that enable optimiza- tion through policy-driven and closed loop automation. The RIC is also poised to create faster and more flexible service deployments and programmability within the RAN. Open Networking Automation Platform (ONAP) is another open source effort to define a comprehensive management and network orchestration (MANO) framework for delivering software-defined networking (SDN) services that support both VNFs as well as CNFs. Both K8S and ONAP are supported by the Linux Foundation and can co-exist to support container modules on top of existing platforms in the operator network. ONAP (see Figure 6.2.5) provides a platform for real-time and policy-driven orchestration and automation of physical and virtual network functions (NFs) that will enable software, network, IT and cloud providers, and developers to rapidly automate new services and support complete lifecycle management ONAP interfaces with three major external subsystems: Operations Support System (OSS), Broadcast Satellite Services (BSS), big data analytics, and e-services applications through the northbound interface (the interface with higher-level layers of software); Virtualized infrastructure manager (VIM), the network function virtualization infras- tructure (NFVI), and the SDN controller jointly constituting the network function virtu- alization (NFV) cloud through the southbound interface (the interface with lower-level layers of software); Design Inventory Policy Configuration RAN Intelligent Controller (RIC) non-RT Orchestration & Automation (e.g. ONAP): MANO, NMS Figure 6.2.4 Orchestration layer (Source: Reproduced by permission of © O-RAN). 3 RIC is currently being defined by O-RAN and is not described in detail in t