 main areas: service orchestration embod- ied in the MSO and service control embodied in the infrastructure, application, and network con- trollers. It illustrates the two major domains in a network cloud that employ orchestration, network service, and network infrastructure. Although the objectives and scope of the domains vary, they both follow a consistent model for the definition and execution of orchestration activities. Building the Network of the Future Homing Service Scope Determination Resource Mgmt. Request Decomposition Service Instantiation Controller Data Flow Mgmt. Request Status/Tracking Obtain SDC A&AI Query Recipes & Update Attributes Attributes Organizes and Manages fulfillment of Orchestration Manages service & network flows, Service or Capacity Requests intimate with network protocols Tracks state of request delivery (Process Execution Engine) Manages the state of application, Collects environmental, situational and network, and infrastructure resources contextual attributes Single service/network domain scope Scoped across multiple control functions Policy-based Immediate impact to active service is Active service is not immediately Pattern Decisions likely if the environment fails affected if the environment fails Scaling Event Resolution Container Cross Container Capacity Mgmt. Capacity Mgmt. Request Rollback Service Controller State Mgmt. Instantiation Controller Create, Manages Topology Mgmt Service Graphs Minutes Performance Sub-Second FIGURE 7.4 Comparison of MSO and controllers (ONAP view). Depending on the scope of a network issue, the MSO may delegate, or a controller may assume, some of the activities identified above. The MSO's job is to manage orchestration at the top level and to facilitate the orchestration that takes place within the underlying controllers; it also marshals data between the controllers such that they have the "process steps" and all the "ingredients" to com- plete the execution of their respective recipes. For new services, this may involve determination of ser