Service and Network Orchestration - L2 Training Videos

This is a brief introduction to  Oracle Communications Service and Network Orchestration Solution.

This session describes the layering of Oracle’s Service and Network Orchestration solution and introduces the architectural components that comprise each layer.

This session walks through a simple end-to-end  example of processing an incoming Product Order using Oracle’s Service and Network Orchestration solution.

This session examines the run-time architectural components found in the Service Orchestration layer of Oracle’s Service and Network Orchestration solution.

This session examines the run-time architectural components found in the Network Orchestration layer of Oracle’s Service and Network Orchestration solution.

This session introduces the Conceptual Model used in Oracle’s Service and Network Orchestration design time environment.  The Conceptual model for a Service Domain provides a unified information model that anchors the design time experience for the solution.

This session illustrates how a Conceptual Model represents the aspects of a Service Domain that are essential for defining Service Orchestration.  We will look at the Broadband Internet Access Conceptual Model and show how each element in the Conceptual Model expresses an aspect of an actual service deployment.

This session explains how a coherent set of application-specific meta-data  is generated from a Conceptual Model in Oracle’s Service and Network Orchestration solution.  This realization process for a Conceptual Model ensures that each application is configured with consistent, aligned meta-data that guides the SNO platform in orchestrating incoming Service Orders for a specific Service Domain and delivering appropriate configuration to the network.

This session introduces the Rapid Service Design Methodology for creating Service and Network Orchestration solutions.  This methodology leverages SNO’s Model-driven development approach as well as the inherent decoupling and encapsulation of implementation artifacts within SNO.  It provides  a predictable pattern for work breakdown and task sequencing. This methodology scales across different sizes of projects ranging from an incremental changes acting on small details of a solution to the implementation of complete new solution domains.

This session provides an overview of the Domain samples that are included in the SNO Reference Implementation. These samples illustrate different service domains implemented in accordance with SNO principles.  Each domain sample represents a category of services with significantly different characteristics, and thus each sample  highlights  details and patterns that are broadly relevant to implementations of services with similar characteristics.