n be sent to the component using the model, in advance of when they are needed or (2) models can be accessed in real time by the runtime components. This distribution is intelligent, such that each function automatically receives or has access to only the specific model components, which match its needs and scope. 7.4 SOFTWARE-DEFINED CONTROLLERS 7.4.1 APPLICATION, NETWORK, AND INFRASTRUCTURE CONTROLLER ORCHESTRATION As previously stated, orchestration is performed throughout the ONAP architecture by various com- ponents, primarily the MSO and the application, network, and infrastructure controllers. Each will perform orchestration for one or more of the following: 1. Service delivery or changes to existing service 2. Service scaling, optimization, or migration 3. Controller instantiation 4. Capacity management Regardless of the focus of the orchestration, all recipes will include the need to update A&AI with configuration information, identifiers, and IP addresses. 7.4.2 INFRASTRUCTURE CONTROLLER ORCHESTRATION Like the MSO, controllers will obtain their orchestration process and payload (templates/models) from SDC. For service instantiation, the MSO maintains overall end-to-end responsibility for The Network Operating System ensuring that a request is completed. As part of that responsibility, the MSO will select the appro- priate controllers (infrastructure, network, and application) to carry out the request. Because a service request often comprises one or more resources, the MSO will request that the appropriate controllers obtain the recipe for the instantiation of a resource within the scope of the requested controller. After service placement is determined, the MSO may request the creation of a VM at one or more locations depending on the breadth of the service being instantiated and whether an existing instance of the requested service can be used. If new VM resources are required, the MSO will place the request to the infrastructure controller for the specific network cloud loca- tion. Upon receipt of th