OSSera Delivers Resource/ServiceActivation System
Resource Activation and Service Activation Management are important components in Resource and Service Management Domain of Operations Support System (OSS). Resource activation applications interpret the needs of a fulfillment request into specific control commands for a network or sub-network often handling proprietary messaging with individual resource elements, whereas service activation application is responsible for activation of specific services based on the specific service configuration.
OSSera has developed Service Activation System (OSSera SA) under the general guidance of TMF Frameworx to provide quick FFTH connections and services through efficient and effective tools that have the following functionalities:
· Update the resource instance to perform the activation or deactivation
· Update the resource to activate Billing data collection
· Notify Resource Provision / Control of the activation status
· Update Resource Inventory with the resource status information
· Queued / scheduled activation requests
· Configuration validation and rollback
· Manage dependencies within, and across network elements through rules
· Multi-vendor and multi-technology activation
· Multiple NE activation coordination
· Confirm / identify available resources
- Provide notifications on successful activation; in cases of exceptions send fallouts to Service Order Orchestration and manage rollbacks activities (if applicable)
Two major tools of OSSera SA are the flow designer and flow executor. The flow designer is for user to design service activation process flow. This involves the processes of understanding the network technology, network topology, device (interface and command set), EMS functions (interface and command set), and the service provided to customer. For each service activation process, identify the steps to provision the network (devices) and commit the resource to activate the service. Each step includes the processes to identify the devices (or EMS) to be involved and corresponding interface and command set to be used to provision the device then commit the change of configuration in device. It also involves the process to understand and carry out the roll back steps when failure happens. With all these processes done and knowledge collected, the service activate process flow can be designed using the flow designer. The designed flow then will be debugged to ensure each step is correctly implemented in the debugger tool of OSSera flow designer. When the service activation flow is verified, it is ready to be executed in production environment by operators. The flow designer also comes with tools to design flow execution reports. Flow execution details can be designed into reports so that management team and technical team can look at the reports to help them to make business and technical decisions.
The flow executor is another set of tools for operators to carry out the service activation process. The processes include find the proper service activation flow, providing correct information then monitor the flow execution. In the case of abnormality, service activation flow can be manually interrupted or completely stopped. The flow executer also comes with report viewer so that user can view past flow execution.
The following diagram shows the software architecture of OSSera SA:
OSSera SA is mainly consisted of the following components:
· SAServer – SA server is the back-end process for service activation. It takes order from user, maps the order a circuit then calls the activation flow to carry out the provisioning process. If the service activation process fails in flow execution, it will roll back any changes. If the service activation process succeeds, it will update inventory to reflect the status of devices in service.
· CORBA – The communication technology used among OSSera systems.
· Flow Engine – The engine to execute process flow. It is choreographs works done inside the server (OSSera program) as well as orchestrate calls to external system or command by using OS utilities or 3rd party API.
· Report Viewer – The graphic interface to view flow execution reports.
· Object Viewer – The GUI component for operator to view MO (managed object) in graphical view, such as network or service topology view.
· MO View – The tree view to see and edit MO attributes as well as relationships to other objects.
· User Management View – A set of GUI components to view, create, update and delete user and related information such as authentication and authorization.
OSSera SA can be deployed in the form of primary-secondary (see diagram below) or symmetric distribution.